I’m a retired Unix (AIX) admin and I run some Linux servers at home. But, I’m still using Windows as a desktop. This whole Windows recall thing is the final straw - I’m switching to Linux for desktop. I’ve done a bit of research and believe Debian is the best fit for me. So, I recently installed it on one of my small servers.
I like it but I find the “half baked” approach to systemd a bit confusing. My default minimal server install has both cron jobs and systemd timers configured for basic system maintenance tasks. For example logrotate is fired twice a day - once by /etc/cron.daily/logrotate and once by /lib/systemd/system/logrotate.service. I’m tempted confirm that everything cron does is actually also done by systemd and then apt purge cron\* && rm -rf /etc/cron*. But, I suspect that might break future package installs and updates?
I’m also not excited by ifup/ifdown - why not just use the capability already included with systemd? This is just a minor thing for me as there’s no real duplication I guess.
Is the a Debian based “pure systemd” distro??
Logrotate has a configuration trigger and if your system has systemd, it uses systemd timer.
Don’t remove cron, some packages depend on it such as apt, etc. ^^;
Oops, too late. It’s just a very simple single purpose system - I can deal with broken things and removing cron on this box is kinda a test to see what breaks. I checked the apt cron jobs and they also seemed to be duplicated as systemd timers - but it wasn’t a very thorough check. My logs show apt-daily.service being run daily by systemd.