cross-posted from: https://lemmy.world/post/24764351
I dislike journalctl more than systemd. And I don’t get what’s the advantage of systemctl vs previous solutions, why would that of all things make one reconsider.
I miss rc.local and crontabs. Now if you excuse me I have a cloud to yell at.
The only advantage I see is that it actually seems to keep a better handle on the status of the process/service. The old-style unit scripts would often get out of sync and not realize that a process had died, or if they did they would repeatedly respawn a service that would just die again. Maybe that was less of a problem in later years than I experienced earlier, but it was there.
The whole init.d system felt very ad-hoc with every script working a little bit differently, giving different output styles, etc.
I learned systemd first so its comfy 🤷♀️
I feel that. I’ve used Linux before systemd but when I went into the “nitty gritty” by using arch systemd had just been implemented and everything I learned about startup services init etc. was systemd based. When I started my career working in servers they were redhat/CentOS so still systemd and when I switched jobs Debian already had made the switch so (most of) the systems at my new job were also systemd based. Of course I learned the basics of init files and even some rc.d but systemd still makes the most sense to me and like you say it’s “comfy”.
@pewgar_seemsimandroid systemd has a lot of really good things…
But it’s too complex for init process and even too complex for service manager. Many solib dependencies causes long start, big memory footprint and possibe security issues. Many things might be implemented in some separate services, running with restricted permissions and optionally disabled.
initng was very similar to systemd, but was very simple and very much faster
{insert IBM conspiracy here}
Anyone got a good tutorial/guide fir SystemD?
Figure I may as well try to wrap my head around it if it’s supposedly going to murder me in my sleep or whatever.
And if you’re not a 50 year-old Linux admin, Arch wiki.
Edit: don’t be put off by the Arch wiki if you don’t use Arch. 99% of the time, Linux is Linux, and you can follow it for just about anything other than package management.
That too but arch wiki sometimes doesn’t list all the possibilities the program can do or not, skill issue if you can’t read.
