4 ms·
I'm sorry. But the "Unix" way is to do one thing well. Why is it that every single app needs to support a "daemon" mode? It is the biggest pain in the but. I
by jbverschoor 9y ago
I'm sorry. But the "Unix" way is to do one thing well.
Why is it that every single app needs to support a "daemon" mode?
It is the biggest pain in the but.
I love systemd. Finally a sane solution on linux.
- JdeBP 9y agoYou weren't looking very hard for such solutions, obviously, as you missed 20 years of stuff. The idea that applications do not have to have their own code to daemonize had been around for about a decade and a half before systemd was even an idea, and there were plenty of toolsets that one could employ to manage daemons where exactly this idea was part of the design. I myself was explaining not to make this design mistake before the turn of the century. * http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.ht... * http://jdebp.eu./FGA/daemontools-family.html http://jdebp.eu./FGA/daemontools-family.html * http://blog.darknedgy.net/technology/2015/09/05/0/ http://blog.darknedgy.net/technology/2015/09/05/0/
- kpil 9y agoYes it's nice to have a proper process manager. Is just that it's obvious that the feature creep tendencies are strong, and a lot of tangential daemons and tools are affected. All in all, I've come to the conclusion that it's probably for the better, but I must admit that even small things like an embedded 'more' implementation seems a bit off somehow.
- phil21 9y agoYou like the one sane thing systemd does - very few folks argue that it's implementation of unit files and friends is a bad thing. Other init systems were progressing in the same direction though. The problem is everything under the hood. Have you ever tried to debug a wedged Linux server with a somewhat esoteric startup issue these days? It's exceedingly difficult, and not simply because you need to learn an new tool chain. It's simply made many things opaque and replaced other bits no one sane would ever expect (e.g. having to remember systemd re-implements 'rm' and the quirks that brings, etc.) As a cranky systemd-hater I also love the unit/service files - they work great, and as you say one tool that does it well. And systemd excels at making any random program a reliable and standardized daemon. Why does it also need it's own dns resolver? If I were simply an end-user or developer making apps to run on linux I'd love systemd. It's when you're maintaining the bare metal where you start to see it's lesser known and more ugly parts.