2 ms·
I've actually gotten to the point where I don't mind systemd itself ("systemctl status" is a sysadmin's wet dream, and the built-in security and resource limit
by amyjess 12y ago
I've actually gotten to the point where I don't mind systemd itself ("systemctl status" is a sysadmin's wet dream, and the built-in security and resource limit options are seriously wonderful), but what I do have a problem with is how the Linux ecosystem is turning into a monoculture.
IMO, Linux is at its healthiest when its two most popular server distributions, RHEL and Debian, are as different as they can possibly be. I really wish Debian would have gone with OpenRC for that reason.
- vezzy-fnord 12y agobuilt-in security and resource limit options are seriously wonderful You could have used these already as separate tools that operate on process state. It's just kernel subsystems and syscalls at the end of the day. util-linux has them.
- amyjess 12y agoBut with systemd, I can just throw an extra key-value pair in the unit file, and bam. No messing with wrapper programs, no modifying the service's code and recompiling, etc. It's not that it's not possible without systemd, it's that systemd makes it trivially easy.
- vezzy-fnord 12y agoIt's either throw an extra key-value pair or throw an extra program name in front of the line to start. They're both trivially easy, and the latter has the advantage of being totally agnostic of anything other than the kernel.