[systemd-devel] remote-fs dependency/ordering on network

[Jan Synacek]

Lennart Poettering <lennart at poettering.net> writes:

> On Mon, 22.06.15 14:49, Jan Synacek (jsynacek at redhat.com) wrote:
>
>> Lukáš Nykrýn <lnykryn at redhat.com> writes:
>> 
>> > Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
>> >> Is remote-fs.target somehow dependent/ordered on network.target or
>> >> network-online.target? I can't find anything that would suggest it
>> >> actually is.
>> >> 
>> >> Cheers,
>> >
>> > If I am not mistaken remote-fs.target should be after all netdev mounts
>> > and netdev mounts should be after network-online.target.
>> 
>> I'm sure it should, but I don't see any evidence that it really is. My
>> mnt-nfs.mount that was generated by the fstab generator is ordered
>> before remote-fs.target, which is correct. However, I can't find any
>> dependency between remote-fs.target, and network*. I'm quite puzzled how
>> NFS mounts mounted on boot can actually work correctly right now.
>
> There's also remote-fs-pre.target. That's ordered before all NFS
> mounts, and that's what the online stuff should be ordered before.

All seems to be in order when the system is booting up. However, during
shutdown, the order in which network* and remote* are taken down seems
to be incorrect. If you could take a look at [1], that would help a bit,
since I'm really clueless right now.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1214466

Cheers,
-- 
Jan Synacek
Software Engineer, Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150623/f770a32e/attachment-0001.sig>