Skip to main content

Timeline for Cron vs systemd timers

Current License: CC BY-SA 3.0

21 events
when toggle format what by license comment
Sep 19, 2024 at 0:59 comment added swpalmer For the record Amazon Linux 2023 does not include cron by default and suggests that in a future version cron support may not be available at all. docs.aws.amazon.com/linux/al2023/ug/…
Feb 16, 2024 at 4:48 comment added Mark G. Just because it hasn't been said yet, but I think it bears mentioning for those who might not be aware: crontab is POSIX. systemd-timers are not. I would hazard a guess that that's probably how the "Cron is guaranteed to be on any Unix-like system" sentiment originates, which I wouldn't say is necessarily wrong in light of this. In any event, POSIX pedants can just claim that systems that don't comply with it can hardly call themselves "Unix-like", since POSIX is meant to represent a lowest common denominator of Unices.
Jan 30, 2022 at 3:14 answer added Robert Siemer timeline score: 20
Jan 26, 2022 at 12:14 comment added Faheem Mitha @RobertSiemer Actually, one real life case I was recently looking at is using fetchmail (or getmail) to download mail from a server using POP3. But there are dozens of such possible examples.
Jan 26, 2022 at 4:00 comment added Robert Siemer Regarding “one side-by-side comparison of a cron script vs a systemd timers script”: could you hand out at least one use case?
Jan 26, 2022 at 3:56 answer added Robert Siemer timeline score: 5
Apr 24, 2018 at 12:52 history edited tshepang CC BY-SA 3.0
remove apology, and systemd is likely not as controversial as it used to be
Jan 5, 2017 at 7:46 review Close votes
Jan 5, 2017 at 11:34
Jan 4, 2017 at 22:34 answer added shdwlynx timeline score: 29
Dec 5, 2016 at 9:06 review Close votes
Dec 5, 2016 at 10:59
May 5, 2016 at 8:10 answer added FargolK timeline score: 97
Apr 30, 2016 at 3:29 history tweeted twitter.com/StackUnix/status/726252222477127681
Apr 24, 2016 at 8:02 history edited Faheem Mitha CC BY-SA 3.0
added 294 characters in body
Apr 23, 2016 at 15:19 review Close votes
Apr 23, 2016 at 19:33
Apr 23, 2016 at 15:09 comment added Faheem Mitha @larsks It's intended as a reference. In case that wasn't already clear.
Apr 23, 2016 at 14:56 comment added larsks That's quite a list of things you want in an answer. I think maybe you should spend some time learning the tools yourself and see if you can formulate those answers on your own, and if you have specific things you don't understand, ask them here.
Apr 23, 2016 at 14:39 comment added Faheem Mitha @Guido I just meant that it is guaranteed to be available for installation. I didn't men to say it was guaranteed to be installed on any given Unix-like system, though this is probably the case most of the time. On Debian, at least, cron has priority important, though it doesn't try very hard to stop me from removing it. The only thing my system has that actually depends on it is munin, which is a little surprising.
Apr 23, 2016 at 13:52 comment added Guido "Cron is guaranteed to be in any Unix-like system. That is not going to change." – I would strongly debate this. While historically cron has often been included in the base setup of Unix installations, on most systems today it's simply an arbitrary optional software package among others. In fact, there are several popular cron alternatives around (e.g. anacron, fcron, jobber) which may be preferable to cron. cron's functionality is not essential for a system's operation the way systemd or init is, so if you're concerned about current and future portability, I'd rather not place my bets on it.
Apr 23, 2016 at 13:43 history edited Faheem Mitha CC BY-SA 3.0
added 58 characters in body
Apr 23, 2016 at 13:26 history edited Faheem Mitha CC BY-SA 3.0
added 3 characters in body
Apr 23, 2016 at 10:47 history asked Faheem Mitha CC BY-SA 3.0