@mia I need it to run things on a schedule, the logging and other junk is not interesting.


- wake-up / triggers -- any IPC/message bus can fill this role

- namespaces -- jails on BSD, but I can use them with my cron jobs to isolate something I'm running

- state service tracking -- but the timer doesn't do this, it just runs the thing which doesn't have to be a systemd service, and if it is it's probably a one-shot. There are other ways to turn services on/off on a schedule if that's what you really want. Also the timer isn't going to turn the service back on. If it crashes too many times even systemd will mark it as failed. The timer isn't the supervisor here.

So this timer replacement plus something like runit would be suitable for lots of things IMO.