flamingos-cant@feddit.uk to linuxmemes@lemmy.worldEnglish · 16 hours agosystemd is all you needfiles.catbox.moeimagemessage-square81fedilinkarrow-up1927arrow-down16file-text
arrow-up1921arrow-down1imagesystemd is all you needfiles.catbox.moeflamingos-cant@feddit.uk to linuxmemes@lemmy.worldEnglish · 16 hours agomessage-square81fedilinkfile-text
minus-squarebricked@feddit.orglinkfedilinkEnglisharrow-up2arrow-down4·7 hours agoI thought the same, but didn’t we already have things like chron syntax for this? Systemd didn’t have to build its own library.
minus-squareTakios@discuss.tchncs.delinkfedilinkarrow-up13·6 hours agoSystemd’s method is more powerful than Cron syntax.
minus-squarebricked@feddit.orglinkfedilinkEnglisharrow-up5·3 hours agoAight, didn’t know that. I cannot yet imagine any scheduled task that would require anything more advanced than cron (or a similar standalone syntax), but I’ll just trust you with that one.
minus-squarefallingcats@discuss.tchncs.delinkfedilinkarrow-up4·4 hours agoCan you tell Cron to catch up on the things that should’ve happened but didn’t because the system was off?
I thought the same, but didn’t we already have things like chron syntax for this? Systemd didn’t have to build its own library.
Systemd’s method is more powerful than Cron syntax.
Aight, didn’t know that. I cannot yet imagine any scheduled task that would require anything more advanced than cron (or a similar standalone syntax), but I’ll just trust you with that one.
Can you tell Cron to catch up on the things that should’ve happened but didn’t because the system was off?
I think fcron and anacron can do that