A cron job for every man, woman, and child.
  • Voroxpete@sh.itjust.worksEnglish
    37 minutes

    OK, yeah, this is awesome. I will definitely be making use of these tricks in future.

  • HiTekRedNek@lemmy.worldEnglish
    4 hours

    More and more, Linux is becoming Microsoft. “Oh, your system doesn’t run systemd? Good luck using anything else loser!”

  • Bo7a@piefed.caEnglish
    9 hours

    I’ve been doing this stuff for 30 years. The helpful blog post that took 8 pages of text to explain how to schedule a job just made me angry.

    I think I am finally into greybeard territory even though my beard made the change a few years ago. Damn.

    • esc@piefed.socialEnglish
      8 hours

      Why did it make you angry? Do you believe that there are other implementations that do the task better and simpler?

      • corsicanguppy@lemmy.caEnglish
        22 minutes

        Do you believe that there are other implementations that do the task better and simpler?

        All of 'em. If a joke took 8 pages to explain, it wouldn’t be funny either. Lennart’s cancer can go, thanks.

      • Bo7a@piefed.caEnglish
        7 hours

        I was mostly kidding. But the little bit that bothered me was the idea that ‘it is so simple here are 8 pages to barely scratch the surface.’

        cron works fine for me. And if I ever have to work in an environment where I can’t use cron and systemd is available, then of course I will use it. Thus far that has never been the case.

        • corsicanguppy@lemmy.caEnglish
          21 minutes

          where I can’t use cron and systemd is available, then of course I will use it

          I argue for a 5% cost-of-living adjustment for bad software, and I make sure it’s a separate line item so they know it goes away when systemd goes.

        • psycotica0@lemmy.caEnglish
          5 hours

          Yeah, I think it’s just the way the blog post was written. When I was reading it I saw the first few paragraphs was basically “here’s how to do Cron with it”, and then everything after that was “here’s a bunch of other features it has that cron doesn’t and how to use those”

          I don’t think that’s the wrong way to write this kind of article, but I could see it feeling overwhelming on a skim, because it may feel like you need to read the whole thing in order to get anything working. But actually only the start was necessary, and the rest was tasty feature pitch.

  • A_norny_mousse@piefed.zipEnglish
    11 hours

    Kinda agree; I’m surprised how often people use & recommend cron jobs even on systems that have been using systemd for a decade.

    • nous@programming.devEnglish
      11 hours

      Cron jobs are nice and simple to create. Until they go wrong then they are a pain in the ass. You need to manage logging yourself. If you forget you root mail will fill up your disk and crash the system. If you forget the mailto setting. If you remember it you justlose all logs and have no clue why something is not working. You need to redirect the output to a logfile yourself. And then risk filling up the disk with logs unless you remember to also set up logrotate. And you then still don’t know when something last ran or if it ran successfully.

      So many traps and that is just the logging side of things.

      • corsicanguppy@lemmy.caEnglish
        19 minutes

        [your] root mail will fill up your disk and crash the system

        If your ~mail/root is more than 0-length, you’re missing valuable information.

      • qupada@fedia.io
        11 hours

        My favourite - and I’ve gotten into arguments with people about this who clearly never just tried it to see what happens - is it never executes things with the shell you think it will.

        So many people assume that just because their script says #!/bin/bash at the top that cron is going to run it in bash. The reality is without ALSO setting SHELL=/bin/bash in the crontab file, you’re getting your system’s lowest-common-denominator shell (ash/dash/sh/whatever other gross abomination).

        So much time wasted debugging. And I’m generally pretty good at avoiding shell-specific syntax, I’ve seen the abominations of shell scripts some people write.

        The one thing I do wish systemd timers offered is cron syntax backwards compatibility, rather than just its ISO8601-style time patterns. An every-5-minutes job that used to be */5 * * * * is now OnCalendar=*-*-* *:0/5:0 and I’m just not sure that syntax is universally an improvement.

        • 4am@lemmy.zipEnglish
          7 hours

          Other than a re-arrangement of the fields, what is the big difference? Harder for awk to work with?

      • A_norny_mousse@piefed.zipEnglish
        11 hours

        yes and yes and yes, except:

        Cron jobs are nice and simple to create.

        So are systemd timers. Seriously. I understood this sort of argument in the years when systemd was relatively new, but nowadays … c’mon, it’s 2 config files in a very simple (the simplest form is just 2 headings with one variable definition each) and common format and (optionally) one command to reload the daemon.

        Maybe adding a line to your list of cron jobs is slightly quicker, but you have none of the things systemd offers on top.

        OK, tbf I don’t know how much (ana)cron provides. Cleaning up the process tree? Restart conditions? Avoiding service duplicates? Advanced starting & repeating like “5min after boot” or “only after this other service has succeeded”? Can it read abbreviations like ‘daily’ or does it all need to be in that cryptic cron syntax?

        • corsicanguppy@lemmy.caEnglish
          18 minutes

          I understood this sort of argument in the years when systemd was relatively new,

          The ageism creeps out of this one.

        • nous@programming.devEnglish
          11 hours

          Its hard to argue that 2 config files both multiple lines long is simpler then a single line in an existing file. Adding a service to cron is just simpler. But adding all the extra bit you are going to want on top increases the things you need to learn to do and configure correctly.

          IMO systemd timers are simpler to get right at a little bit more of an upfront cost to learning how they work. But cron is still simpler to just get something working without caring that much. I still find that ends up biting you in the longer term though though all the missing features you need to add manually on top of that one basic line you added.

  • Great Blue Heron@lemmy.caEnglish
    9 hours

    This is one of the things that frustrate me about Debian based systems. I know most distributions ship with lots of different tools to do the same job and you pick the one you like. But with something as fundamental as system timers it just feels wrong to me - when I want to change the timing of something I first need to figure out is the cron job real, or just a stub referring to the systemd timer, or visa versa.

    So for a while I had removed cron from all my systems and fully committed to timers. Now I’ve decided I don’t like systemd and gone fully the other way.

    I know it’s not that bad, but that’s the way my brain works - and I can remember getting really screwed up with some early Ubuntu systems.

    • 4am@lemmy.zipEnglish
      7 hours

      Yeah, it’s never fun having both a legacy and a new system at the same time

      Same with sysv and systemd job files. That seems to be mostly cleaned up now but for a while it was a PITA.

    • corsicanguppy@lemmy.caEnglish
      17 minutes

      Never heard of it

      It’s something coded up by a Microsoft employee. Or did he take his toys and move on again?

  • plc@feddit.dkEnglish
    10 hours

    The headline puns made my day❤️