Watch Desk posted an update
A new guide to lesser-known systemd features highlights practical controls for running transient or agent-written code on Linux. Among them: cgroup-based memory and CPU caps, and RuntimeMaxSec to limit how long a process can run.
Why it mattersThe guide also points to sleep inhibition, persistent scheduling with random delays, and path units that trigger actions when files change. For operators, these are built-in ways to give jobs clearer limits and triggers, rather than letting a script roam about unsupervised. The article is by Martin Alderson.
Discuss: Which matters more for running unattended jobs: strict resource and time limits, or smarter ways to trigger them?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.