Re:“I wish systemd would get over its thing about syslog”
by cpncrunch on Saturday April 11, 2015 @01:49PM
(#9360000)
For the servers I run, boot time isn't an issue. I might reboot a server once a year, and booting in 10 seconds vs 40 seconds isn't really an issue. What is an issue for me is stability. I don't really care about "hideous shell scripts" as long as they work.
[ Parent
| on HN ]
Re:“I wish systemd would get over its thing about syslog”
by rwmj on Saturday April 11, 2015 @03:30PM
(#9360422)
Virtual machines, containers and appliances all require very short boot times, because they may be created and booted frequently.
Re:“I wish systemd would get over its thing about syslog”
by digi_owl on Saturday April 11, 2015 @07:33PM
(#9361254)
Sometimes it feels as if these would be better served with the age old DOS flat files than something as convoluted as a *nix init.
This because if a "service"/daemon fails to come up, you may as well scuttle the whole VM/container/appliance and spin up another in its place.
Re:“I wish systemd would get over its thing about syslog”
by hobarrera on Saturday April 11, 2015 @03:02PM
(#9360301)
But linux isn't all about servers, there's a lot of desktop users out there.
And having desktop and server diverge at a kernel/init level seems too much burden to maintain.
Re:“I wish systemd would get over its thing about syslog”
by felixgallo on Saturday April 11, 2015 @03:28PM
(#9360413)
no, there are almost no desktop users out there; certainly, far fewer, probably by two orders of magnitude, than server and embedded installations; and the divergence in favor of doing things the desktop developers' way is very much the tail wagging the dog.