Hey Willy, Willy Tarreau wrote: > I absolutely despise systemd and each time I have to work on the > wrapper I feel like I'm going to throw up. So for me working on this > crap is a huge pain each time. But I'm really fed up with seeing > people having problems in this crazy environment because one > clueless guy decided that he knew better than all others how a daemon > should reload, so whatever we can do to make our users' lifes easier > in captivity should at least be considered.
Just to be sure, I don't like systemd for mostly the reasons you mentioned. However, I do use the systemd wrapper to reliably run HAProxy under runit for a couple of years now. Since they (similar to most service managers) also expect a service to have one stable parent process even after reloading, the systemd wrapper acts as a nice workaround to facilitate reloading. The same wrapper allows simple service handling with Solaris's SMF and is a much better solution than the crude python script I wrote a couple of years ago for this simple process. I guess what I've been trying to say is: the wrapper is absolutely useful for about any process manager, not just systemd and I would love to see it stay compatible with other process managers like runit. Thanks for the great work Willy, here and on the Kernel. Regards, Holger
