It might be trivial for you, but not for me. I like systemd - perhaps because I came to Linux from AIX? Anyway, because I like it, I use it on all 4 of my servers - I have custom systemd unit files for applications I run that don’t natively support it, I’ve removed cron and use systemd timers for all my scheduling and I use systemd’s remote journal capability to centralise logs to my monitoring server.
if you are not used to it you will have to learn it… that goes both ways…
and all the functionality you need were already in normal initfiles, cron and rsyslogd
my main issue with systemd always has been, that it centralises stuff that does not relate to each other into one single program instead of keeping it seperate and as simple as possible
I never said I can’t do it - I’ve been running different varieties of unix for over 35 years. I said it’s not trivial.
And, being a bit pedantic with your terminology - systemd does not “centralises stuff that does not relate to each other into one single program”. systemd, systemd-journald, systemd-networkd, systemd-resolved etc. etc. are all separate programs, provided by the systemd project, with their own configuration. You are free to pick and choose which parts of systemd you use and which you don’t.
All that being said - I am a bit over complexity of modern mainstream distributions and am now considering moving to Apline for my servers.
It might be trivial for you, but not for me. I like systemd - perhaps because I came to Linux from AIX? Anyway, because I like it, I use it on all 4 of my servers - I have custom systemd unit files for applications I run that don’t natively support it, I’ve removed cron and use systemd timers for all my scheduling and I use systemd’s remote journal capability to centralise logs to my monitoring server.
if you are not used to it you will have to learn it… that goes both ways…
and all the functionality you need were already in normal initfiles, cron and rsyslogd
my main issue with systemd always has been, that it centralises stuff that does not relate to each other into one single program instead of keeping it seperate and as simple as possible
I never said I can’t do it - I’ve been running different varieties of unix for over 35 years. I said it’s not trivial.
And, being a bit pedantic with your terminology - systemd does not “centralises stuff that does not relate to each other into one single program”. systemd, systemd-journald, systemd-networkd, systemd-resolved etc. etc. are all separate programs, provided by the systemd project, with their own configuration. You are free to pick and choose which parts of systemd you use and which you don’t.
All that being said - I am a bit over complexity of modern mainstream distributions and am now considering moving to Apline for my servers.