• Phoenixz@lemmy.ca
    link
    fedilink
    arrow-up
    4
    arrow-down
    4
    ·
    2 months ago

    I’m sorry but Cron is really easy, of all systems.

    Try using systemd with an ssh server that you want to have running on a non standard port. On non systemd it’s a 15 second ordeal while on systemd I don’t even know where to start, I pushed it out of my memories. It’s something something create files here, restart demons there, removing other files, it is WAY WAY over complicated

    • offspec@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      What do you mean? You literally just change the /etc/sshd config to point at a different port do you not?

      • Phoenixz@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        Oh yeah, without systemd that’s all there is to it. With systemd, however, port management is taken out of the ssh config and is done how it was decades ago

    • umbraroze@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      Well cron is “really easy” as long as your requirements are really easy too.

      Run a task at specific hour or minute or weekday or whatever? Easy peasy.

      Run a task at complex intervals? What the fuck is this syntax. How do I get it right even. Guess I’ll come back next week and see if it ran correctly.

      Actually have to look at the calendar to schedule this stuff? Oh lawd here come the hacks, they’re so wide, they’re coming

      Run a task at, say, granularity of seconds? Of course it’s not supported, who would ever need that, if you really need that just do an evil janky shellscript hack