• Great Blue Heron@lemmy.ca
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    4 months ago

    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.zip
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 months ago

      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.

  • CriticalMiss@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 months ago

    I dunno, systemd timers seem overcomplicated, cron is simple and universal (as in expected to be on every system install in one of its variants). You only need to learn how to set the time once and if you’re having difficulties setting up time you can use a website crontab.guru

    Cron’s simplicity also makes it bulletproof, it just runs things on a schedule, that’s it. You can’t expect it to crash or give you any trouble.

    • rnkn@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      4 months ago

      I stopped reading when the claim that you shouldn’t use cron was followed with no supporting argument.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      4 months ago

      Never heard of it

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

  • HiTekRedNek@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    13
    ·
    4 months ago

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

      • HiTekRedNek@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        9
        ·
        4 months ago

        No, I’m complaining that things like gnome and KDE all expect systemd and all of its associated other poeterring BS.

        I don’t run Linux AT ALL.

    • mal3oon@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      Tbh, there are lots of variety in linux if you don’t want systemd. Void in particular is really neat, been running it on one of my old 2017 xiaomi “air” notebook, i3 (back when lukesmith was a linux jesus). It’s amazingly stable for a rolling release, and very light compared to my other arch systems.

    • heartSagan5@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      6
      ·
      4 months ago

      Because a lot of Microsoft employees contribute to Linux in their spare time to keep their skills sharp. It says something about a platform when you’re free to work on other platforms.

      Also, Microsoft released Azure Linux.