this post was submitted on 27 Oct 2024
1261 points (99.4% liked)

linuxmemes

21118 readers
2700 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    1261
    systemd is all you need (files.catbox.moe)
    submitted 2 days ago by [email protected] to c/linuxmemes
    117 comments fedilink hide all child comments
     

    Original

    you are viewing a single comment's thread
    view the rest of the comments
    [–] umbraroze 16 points 15 hours ago (2 children)

    Well, systemd developers made one of the classic blunders a software developer can do: make a program that has to deal with time and dates. Every time I have to deal with timestamps I'm like "oh shit, here we go again".

    Anyway, as I understood it the reason this is in systemd is because they wanted to replace cron, and it's fine by me because cron has it's own brain-hurt. (The cron syntax is something that always makes me squint real hard for a while.)

    [–] [email protected] 1 points 13 hours ago (2 children)

    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 3 points 8 hours ago

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

    [–] umbraroze 2 points 9 hours 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

    [–] [email protected] 1 points 13 hours ago

    Yeah and they actually added some usability in the form of that utility helping you debug what you're doing. Pretty nice!