On Di, 28.01.20 10:46, Johannes Ernst ([email protected]) wrote: > Is there a best practice for scheduling .timers based on what happened in a > previous run? > > Pseudocode: > > while( true ) : > delta = runService(); > sleep( delta ); > > I can think of … > > 1) run the job frequently, but skip the bulk of its execution most of the > time (e.g. decrementing a counter saved somewhere) > 2) have the job modify the .timer file at the end of each run (sounds … not > so great) > > There isn’t anything systemd “native” for that, right?
Consider just creating a transient timer unit via the D-Bus API from your service code. Alternatively, use systemd-run for that, which can do that for you from the cmdline. Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
