Re:Systemd Brand
by luckycharms810 on Thursday November 21, 2019 @04:00PM
(#21599555)
I will say on the flip side - Going from cron jobs to Systemd timers has been super helpful. You can use journalctl to track the output and find pesky issues like difference in shell, missing environment variables, file permission issues.
Can you expand on what you feel is over-engineered?
SystemD also fails quietly or with useless errors and makes problems hard to diagnose - so a bug not directly caused by SystemD looks like it comes from SystemD because SystemD slime is on everything - is extremely poorly-documented, extremely over-engineered, and subject to rapid change due to the moodiness and instability of the OverPoetter.