5 ms·
I use systemd to manage the (sort-of) microservices for some web app projects I've done. To me, the unit files are simple and even beautiful compared to the big
by stephen_g 10y ago
I use systemd to manage the (sort-of) microservices for some web app projects I've done. To me, the unit files are simple and even beautiful compared to the big pain that init scripts used to be.
Those old init scripts weren't simple - to do anything useful you had to copy and paste a whole heap of sh boilerplate...
- pmlnr 10y agoNo offense, but this comment only indicated that a syntax is simpler and has nothing to do with the actual quality and stability of systemd. This is my regular problem in systemd arguments. I understand learning init script - and bash as a consequence - can be tiring, but judging a software by how easy or not is it to configure is utterly and fundamentally wrong. After a certain point, systemd is not easier to configure than any earlier system; nor is it any more stable, or, god forbid, easier to replace a part of it. Please stop glorifying things that you're only touched the surfaces of.
- stephen_g 10y agoIt's something that's been reliably working for me over many servers over the last two or three years... I don't care if it's easy to replace bits of - the people who produce the distribution I use can worry about that. All I care about is that it has worked really well for me in production and I have found it much easier to use and maintain than older systems.
- Sanddancer 10y agoCopy/paste was the real problem, not init scripts. Look at the init scripts of FreeBSD some time. They're short, well-documented, and built around reusable components. SysV init was a mess because init scripts became a cargo cult of copy-paste, rather than actually using all the capabilities that were available.