2 ms·
> Why do you think that is? Why have production grade Linux distributions all chosen to adopt systemd? Because RH funds a lot of software development, and Poet
by throw0101a 7y ago
> Why do you think that is? Why have production grade Linux distributions all chosen to adopt systemd?
Because RH funds a lot of software development, and Poettering works for them.
> Journalctl is far better than `tail -f /var/log/starstar`
Except when journald shits the bed and corrupts its own log file. Or when you want ship logs off-machine, yet journald does not support any standards-compliant transport so you end up have to log a second logging daemon (e.g., rsyslog)—in which case what's the damn point of the first? Or when you do a "service mysql start" and it dies, but there is no output anywhere of what went wrong, and you have to guess that you have a typo in your "my.cnf".
But other than that Mrs. Lincoln, how was the play?
> ... in an /etc/init.d shebang without process restarting (and logging thereof), cgroups, and consistent logging.
The problem is not systemd-as-init-replacement. The problem is systemd-as-kitchen-sink. udevd is an "essential" part of systemd? Really? It can't be it's own stand-alone project? Really?
- bscphil 7y ago> Or when you do a "service mysql start" and it dies, but there is no output anywhere of what went wrong, and you have to guess that you have a typo in your "my.cnf". First of all, it's systemctl you want, not service. Service is (was) part of Upstart, which Ubuntu doesn't officially use any more but they still have a bunch of compatibility layers in for it. Second, do the following not give you the information you need? systemctl status unit-name journalctl -u unit-name
- westurner 7y agoWhen journald logfile corruption occurs, it's detected and it starts writing a new logfile. When flatfile logfile corruption occurs, it's not detected and there are multiple logfile formats to contend with. And multiple haphazard logrotate configs. Here's how to use a separate process to ship journald logs - from one file handle - to a remote logging service: https://unix.stackexchange.com/questions/394822/how-should-i-send-systemd-logs-to-a-dedicated-logging-server https://unix.stackexchange.com/questions/394822/how-should-i... While there is a systemd-journal-remote, it's not necessary for journald to try and replicate what's already solved and tested in rsyslog and syslog-ng. It's quite a bit more work to add every new service to the syslog-ng or rsyslog configuration than to just ship one journald log. Furthermore, service start/stop events are already in the same stream (with the same timestamp format) with the services' stdout and stderr. Why hasn't anyone written fsck for corrupted journald recovery? ... I have not needed to makedev and chown and chatted and chcon anything in very many years. When you accidentally newbishly delete something from a static /dev and rebooting doesn't work and you have no idea what the major minor is or was, it sucks bad. When you're trying to boot a system on a different machine but it doesn't work because the NIC is in a different bus, it's really annoying to have to symlink /dev or modify /etc. With udevd, all you need to do is define a rule to map the busid device name to e.g. eth0. I can remember encountering the devfs race condition resulting in eth0 and eth1 being mapped to different devices on different boots; which was dangerous because firewall rules are applied to device names. Udev has been in the kernel since 2.6. "What problems does udev actually solve?" https://superuser.com/questions/686774/what-problems-does-udev-actually-solve https://superuser.com/questions/686774/what-problems-does-ud... With integrated udev and systemd, I have no reason to run a separate hotplugd with a different config format (again with no cgroup support) and a different logstream.