• esc@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 hours ago

    You can explain timers the same way.

    And then with your explanation it goes: cron job doesn’t execute for reason, crontab -l lists not all jobs, someone else put cron job in whatever directory like cron.daily, you’ve added or removed empty line at the end and now nothing works, debian crond and redhat cronie ahave different quirks, etc., etc.

    I’ve dealt with insane cron problems for so long that switching to timers was like *whoa i don’t need to suffer?*

    • JTskulk@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      Maybe I’m just lucky that I haven’t run into insane cron problems :) I’ve done both, I guess I just need to do more systemd timers and get used to it. I found it so confusing and weird to set up.

      • esc@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        24 minutes ago

        I’ve always had either problems with schedules or problems with environment because it has it’s own. Cron is fine as long as you are lucky. That isn’t to say there never were problems with timers, on debian 9, I think, shipped version of systemd had a bug where systemd-analyze parsed schedule correctly and timer just shit itself. But only for some specific case I can’t remeber which, but it was extremely frustrating to debug.