[systemd-devel] [PATCH] core: Make sure a stamp file exists for all Persistent=true timers

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Sat Apr 5 08:30:01 PDT 2014


On Sat, Apr 05, 2014 at 11:35:24AM +0200, Tom Gundersen wrote:
> On Wed, Apr 2, 2014 at 8:18 PM, Thomas Bächler <thomas at archlinux.org> wrote:
> > If a persistent timer has no stamp file yet, it behaves just like a normal
> > timer until it runs for the first time. If the system is always shut down
> > while the timer is supposed to run, a stamp file is never created and
> > Peristent=true has no effect.
> >
> > This patch fixes this by creating a stamp file with the current time
> > when the timer is first started.
> 
> If timers are started at early boot (which sounds like a common
> scenario), I guess /var will not yet be writable so this will be a
> noop, no? Maybe it would be better to write out these files at
> shutdown instead (before unmounting anything)?
Isn't timers.target starter after sysinit.target, i.e. after /var has
been mounted?

Zbyszek


More information about the systemd-devel mailing list