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
    you are viewing a single comment's thread
    view the rest of the comments
    [–] 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