[systemd-devel] After in new var-lock.service
Lennart Poettering
lennart at poettering.net
Wed Aug 18 17:24:28 PDT 2010
On Wed, 18.08.10 21:31, jean-michel.pollion at laposte.net (jean-michel.pollion at laposte.net) wrote:
>
> > It creates stuff in /var/run that is only needed when an empty tmpfs
> > is mounted there. If /var/run is on disk, none of these things is
> > needed, but old stuff would need to be deleted instead. The .service
> > is just the extension of the .mount, and does not make sense on its
> > own.
>
> OK
> But what I don't understand is, if the call to var-lock.service after var-lock.mount is implicit, why does var-run.service also need a
> "After=var-run.mount"? Both var-lock.service and var-run.service have the same "After=var-run.mount".
This is just a copy/paste mistake. I have fixed this now. Thanks for
pointing this out!
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel
mailing list