1 point

Okay this is cool and all, but why would systemd have a calendar?

(also how do i do this)

permalink
report
reply
2 points

As others have said on this thread, it’s because systemd has fairly advanced timer system that basically requires implementing a calendar.

To do it, the command is in the screenshot systemd-analyze calendar "Tue *-12-25".

permalink
report
parent
reply
23 points

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.)

permalink
report
reply
0 points

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

permalink
report
parent
reply
5 points

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

permalink
report
parent
reply
1 point

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

permalink
report
parent
reply
2 points

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

permalink
report
parent
reply
1 point

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

permalink
report
parent
reply
0 points

Just write your own initialization system in bash. It is more reliable and less bloated.

permalink
report
reply
21 points

This is basically just a way nicer, more flexible cron syntax being dressed up as something ridiculous. There are legitimate reasons for wanting something like this, like running some sort of resource heavy disk optimization the first Friday evening of every month or something.

permalink
report
reply
8 points

Systemd ignored my calendar override for the builtin raid scanner, so every week my server would chug to a halt to scan the entire array.

In true systemd fashion, the documentation could not explain this behavior, so I had to make a full copy override instead of a merge override because reasons.

permalink
report
reply
4 points

Did setting OnCalendar to the empty string not work? https://unix.stackexchange.com/a/479745

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

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 users for any reason. This includes using blanket terms, like “every user of thing”.
  • Don’t get baited into back-and-forth insults. We are not animals.
  • 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, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.

 

Please report posts and comments that break these rules!


Important: never execute code or follow advice that you don’t understand or can’t verify, especially here. The word of the day is credibility. This is a meme community – even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don’t remove France.

Community stats

  • 7.4K

    Monthly active users

  • 1.4K

    Posts

  • 76K

    Comments