[systemd-devel] fstab generator and nfs-client.target

[Andrei Borzenkov]

В Sat, 25 Jul 2015 12:50:39 +0200
Michael Biebl <mbiebl at gmail.com> пишет:

> 2015-07-25 3:18 GMT+02:00 Rich Freeman <r-systemd at thefreemanclan.net>:
> > I noticed that mount units for nfs shares created by the generator do
> > not Want=nfs-client.target or similar.
> >
> > That means that if you don't explicitly want nfs-client in your
> > configuration then nfs shares will get mounted, but services like
> > rpc-statd-notify.service won't run.
> >
> > Would it make sense to have the generator add the nfs-client target as
> > a want to nfs mount services it creates?
> 
> remote mount units do have a "After remote-fs-pre.target" ordering and
> tools like nfs-common/rpcbind are supposed to hook up into
> remote-fs-pre.target.
> 

They are supposed to be /ordered before/ remote-fs-pre.target; but I do
not remember that remote-fs-pre.target itself was intended to pull
anything. This was designed as pure synchronization point.

> http://www.freedesktop.org/software/systemd/man/systemd.special.html#remote-fs-pre.target
> 

--><--
Note that this unit is generally not part of the initial transaction,
unless the unit that wants to be ordered before all remote mounts pulls
it in via a Wants= type dependency.
--><--

So if I read it, nfs-common should pull in remote-fs-pre, but that
leaves question what should pull in nfs-common itself.