[systemd-devel] systemd unit timer

[Kenneth Porter]

On 8/10/2020 12:19 PM, Dave Howorth wrote:
> Most of that has gone over my head so some examples would probably help
> me to understand. Perhaps they're in the git logs?

The key word is "activation". Modern systems are event-driven. Events 
include hardware plugging in, powering up, another program starting, or 
a point on the calendar. systemd launches programs when events happen. 
That's activation. In the past, activation was handled by lots of 
independent subsystems (initscripts, xinetd, cron) and they had the 
potential to conflict. Now it's all handled in one place and one way. 
Which eliminates a lot of duplication of effort. It means you don't need 
to fix the same bug in multiple subsystems.