News for hackers. Stuff that matters.
Re:Working with Systemd Timers by ForTheKidz on Friday March 14, 2025 @01:47AM (#43359939)
Putting aside that this is all possible with nix and without systemd, the additional complexity strikes me as having hamstrung the linux community for the last decade. I hope reliable service management arises but I have yet to see the benefit.

In the meantime I'm just going to keep using void because I know how to fix it when it breaks. Systemd i have to google how to even find the service logs.... they certainly aren't easy to find via the filesystem any more.

Re:Working with Systemd Timers by Cyph0n on Friday March 14, 2025 @10:31AM (#43362985)
Like I said, it is a bit intimidating at the start. But you soon realize it’s quite intuitive.

Finding logs for a specific service is a one-liner:

  journalctl -u rclone-photos-sync.service
Add -r (reverse) to return newest logs first. Add -b to limit logs to the current boot.

Here is a nice overview: https://www.digitalocean.com/community/tutorials/how-to-use-...

Re:Working with Systemd Timers by gf000 on Friday March 14, 2025 @11:11AM (#43363407)
Well, above a level tools can't be designed to be discoverable without any form of help/learning, and I believe that's fine. They should rely on a "common knowledge base" as much as possible, and I believe systemd commands are done in a POSIX-y style, but you do have to occasionally read a man page or Google.

Do we expect an average dude to just pop into a cockpit and land a plane with no previous training?