On Sun, 18 Jan 2015 15:06, Cristian Rodríguez
El 18/01/15 a las 10:41, Yamaban escribió:
/usr/lib/cron/run-crons contains the logic to make sure calls are done, even when the machine was off at the 'normal' calling time.
Yes and this logic also exists in timers, the unit I wrote had "Persistent=true" but someone commented it..because it was not a supported option at the time (not implemented in systemd 210)
That would mean: - Either SLE12 gets a newer systemd that supports "Persistent=true", or - We will have to depend on /usr/lib/cron/run-crons for the whole SLE12 support period. Choose your poison. Nice. (Urgs, that decision will involve more politics than reason) IMHO, using /usr/lib/cron/run-crons for SLE12 is less work, and has no known errors (so far). For OSS.next (Factory / Tumbleweed) the binding point is the support of "Persistent=true" in systemd. Before that is secured, /usr/lib/cron/run-crons is the only valid and user friendly way to go. Whether it is called from cron or from systemd *.timer unit that is an other matter. Question, is there a "replacement" for the "at" command? I mean a front-end for systemd.timers, usable like the "at" command. -- Or could that be a idea for a GSOC mini-project (entry level, shell/perl/python script + man.page)? - Yamaban.