What are some significant differences to expect when switching to an alternative, and can that affect gaming compatibility and performance?

  • mholiv@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    2 hours ago

    I think if you know cron from the start it can be easier, but it gets really annoying really fast.

    Compare:

    0 0 * * * /usr/bin/flock -n /tmp/myjob.lock bash -c 'sleep $((RANDOM % 3600)) && /usr/local/bin/myjob.sh'
    

    To:

    [Timer]
    OnCalendar=daily
    RandomizedDelaySec=1h
    

    That and things like systemd preventing overlapped delays, handing what to do if the system was down during the last cycle, built in logging and event tracking. Seeing successful vs non successful runs etc.

    Once you add in those production requirements cron gets annoying fast and timers are easy.

    • KeithD@lemmy.nz
      link
      fedilink
      arrow-up
      1
      ·
      54 minutes ago

      For adding a quick thing to make something happen at a specific time, I can add a cron job in a couple of minutes. To add a timer takes creating a couple of files with syntax that took me a while to look up last time I needed it, and running a command. Then debugging. Sure, the timer has benefits, but cron jobs are still simpler.

      On the bright side, there’s actually a “crontab -t” command that apparently can be used to generate timer files from a crontab line, which I hadn’t known of before today.