I am on Mint XFCE and Redshift is just so inconsistent and I have tried its forks, also inconsistent. So instead I have been using sct in the terminal to adjust the temperature, and have set a command that resets it back to normal every time that I log on. However, I was wondering if there is a way to make it so that “sct 2750” runs every day at 10 pm or during a specific period of time.

  • jsveiga@sh.itjust.worksEnglish
    71·
    1 year ago

    “simply no reason”?

    What about ease of use, simplicity, faster to quickly setup, backwards compatibility, and “crobtab is where everyone will look at when looking for a scheduled task”?

    If systemd was implemented right, it would create the systemd files and autoconfigure default tasks by reading the crontab, for backwards compatibility.

    • Ullebe1@lemmy.mlEnglish
      11·
      1 year ago

      What about ease of use, simplicity, faster to quickly setup, backwards compatibility,

      The syntax of systemd timers is MUCH easier to read for newbies (and everyone else, really) as it uses words instead the placement of the characters on the line to convey meaning. If you can’t remember or don’t know the syntax well you can still understand a systemd timer, but that is much hard for the crontab. Granted, crontab uses fewer characters, but if you only set up either once in a blue moon you’ll need the docs to write either for a long time. And is backwards compatibility really an issue with either one? All major desktop and server distros use systemd, and has for a while. Fedora doesn’t even include a Cron by default anymore.

      “crobtab is where everyone will look at when looking for a scheduled task”?

      If it was a distro release from the last decade I’d definitely start by checking the systemd timers, rather than the crontab.

      If systemd was implemented right, it would create the systemd files and autoconfigure default tasks by reading the crontab, for backwards compatibility.

      You can to totally do this, using this systemd generator.

      • the_sisko@startrek.websiteEnglish
        2·
        1 year ago

        If you can’t remember or don’t know the syntax well you can still understand a systemd timer, but that is much hard for the crontab.

        I will agree that it is easier to read a timer than a Cron entry, especially if you’ve seen neither of them before.

        Granted, crontab uses fewer characters, but if you only set up either once in a blue moon you’ll need the docs to write either for a long time.

        This is where I disagree. I very rarely setup a Cron job, but when I do, I don’t need to look anywhere for docs. I run crontab -e and the first line of the editor contains a comment which annotates each column of the Cron entry (minute, hour, dom, mon, dow). All that’s left is to put in the matching expressions, and paste my command.

        Compare that to creating a new timer, where I need to Google a template .service and .timer file, and then figure out what to put in what fields from the docs. That’s probably available in the manual pages, but I don’t know which one. It’s just not worth it unless I need the extra power from systemd.

        This is from somebody who has several systemd timers and also a few Cron jobs. I’m not a hater, just a person choosing the best and easiest choice for the job.