Originally posted by monraaf
Systemd has adjustable timeout values. So that wait time on shutdown can in fact be adjusted. If a system is stalling on shutdown with systemd this means that systemd is detecting something that has been given a shutdown instruction and not doing it. Systemd system without some third party software being defective shutdowns faster than sysvinit by a large margin. Systemd slow to shutdown you either mask out by adjusting the timeouts on how long it waits for miss behaving software or fix the miss behaving software that is not systemd.
Originally posted by monraaf
Originally posted by monraaf
Yes the go away eventually is just you wanting to put head in sand instead of facing up to the problems and learning something new.
Yes the Unix philosophy is a fools item here. Reality is sysvinit does not do one thing right on a Linux kernel. sysvinit fails the Unix philosophy test of "Make each program do one thing well." in every single part. Systemd is in fact multi applications many of those do conform to Unix philosophy of do one thing well.
devuan like it or not it default of sysvinit does not work well. Some of the problems people complain about like the stalling shutdown problem happen when you use a solution that works we because is a sign that you have other software problems that are not systemd/openrc/shepherd that need to be fixed because this can be why at times you can have major data loss.
Systemd does not do everything wrong. Some things people complain about with systemd is because systemd is doing it right and sysvinit was doing it wrong.
Sysvinit lets just brute force kill the system on shutdown without picking up that a service has not shut down properly who cares how much data this destroys lets not give the user a sign that there is anything wrong either. That is exactly what has been going on. Systemd/openrc(with cgroups)/shepherd fixes this problem at the price that when you have something broken in your system your shutdown will be longer unless you alter the default timeout values.
On system with services and applications that shutdown properly systemd and shepherd shutdown faster than sysvinit and openrc every single time.
Really lot of the arguments against systemd are like this where they are incompetence being used to ignore a detected problem just because is a problem systemd detects and attempts to handle correctly that sysvinit never handled correctly.
Leave a comment: