[systemd-devel] [PATCH 07/10] units: order remote-fs.target after local-fs.target

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Wed Jul 16 05:50:39 PDT 2014


On Wed, Jul 16, 2014 at 12:57:41PM +0200, Tom Gundersen wrote:
> On Wed, Jul 16, 2014 at 12:09 PM, Jon Severinsson <jon at severinsson.net> wrote:
> > From: Michael Biebl <biebl at debian.org>
> >
> > This change was part of the old debianisation branch created by Tollef
> > and reflects the fact that on Debian the $remote_fs system facility
> > depends on $local_fs.
> 
> If this is merely for sysv compat, it feels wrong to add this in the
> native unit files (but maybe the argument could be made regardless?).
> If it is just for bacwards compatibility, I would rather put it in the
> sysvgenerator itself (to add a drop-in if something pulls in
> $remote_fs).
> 
> Not sure if this should be upstream or downstream though, depends if
> this makes sense outside of Debian.
No, tying those targets doesn't make much sense. It does not provide anything
for the services which are part of remote-fs.target, they have to carry
their own dependencies on local-fs.target if necessary. So the only
thing it does is that it'll delay remote-fs.target if it were to be
reached before local-fs.target.

Zbyszek


More information about the systemd-devel mailing list