4 ms·
> Except that the problem doesn't exist outside discussions of except https://en.wikipedia.org/wiki/Init#Replacements_for_init https://en.wikipedia.org/wiki/I
by RubyPinch 12y ago
> Except that the problem doesn't exist outside discussions of
except https://en.wikipedia.org/wiki/Init#Replacements_for_init https://en.wikipedia.org/wiki/Init#Replacements_for_init
this problem was noticed and was trying to be fixed for a long time, by a lot of people
- dschiptsov 12y agoTraditionally, one of the major drawbacks of init is that it starts tasks serially, waiting for each to finish loading before moving on to the next. When startup processes end up I/O blocked, this can result in long delays during boot. For a server it doesn't matter, leave alone "broken". long delays during boot is grossly exaggerated, because delays are mostly due to network errors/timeouts or file-system checks, but you can do almost nothing "in parallel" without clean FS or configured network interface. Well, for some Ubuntu for mobile devices they could have adapt some "optimized" sysvinit-scripts (not /sbin/init) replacement, but, please, don't tell us that everyone needs this. Leave servers and home workstations alone.
- RubyPinch 12y agoit matters with servers too, billing-per-hour/minute/second etc and my point was there has been a whole bunch of prior attempts at changing init, each one of those had issue with the pre-existing systems. I am not telling you that everyone needs it, or that its broken. I'm telling you that the issues didn't suddenly exist just because systemd