4 ms·
It's probably been a while since you've last used OpenRC, and I don't know how it was back then, but these days, service scripts are really trivial to write[1].
by mid-kid 3y ago
It's probably been a while since you've last used OpenRC, and I don't know how it was back then, but these days, service scripts are really trivial to write[1]. You just need to provide the command= and command_arguments= to use, and depending on whether the daemon backgrounds itself or not, configure the pidfile location or set command_background=true. It really couldn't be easier.
Personally I just wish it had any notion of logging stdout/stderr, or a way to manage daemons as a user.
[1]: https://github.com/OpenRC/openrc/blob/master/service-script-guide.md https://github.com/OpenRC/openrc/blob/master/service-script-...
- gerdesj 3y agoI migrated to systemd, wholesale. You have piqued my interest and I will spin up a VM at work and have another look at the state of the art on Gentoo. I absolutely loved it back in the day. Every few months or so a major change would arrive and make life better. Sets - @world etc - smashing. User patching - drop a patch in a suitable directory and effectively you could fix snags yourself without having to write your own ebuild. Do your own ebuilds - again drop your override into the right directory and your personal ebuild is seamlessly part of the distro. No doubt much more has happened in the roughly five years when I have used it in anger. Ironically enough I have two systems at work that do run Gentoo but are woefully "legacy". Today I emerged a couple of packages to fix something on one of them and it is still hanging on in there. It is quite a delicate dance on a rather crucial system. I will get rid of it eventually but one step at a time 8)