Michael Biebl <bi...@debian.org> writes:

> Am 20.08.2013 00:51, schrieb Michael Biebl:
>> Am 20.08.2013 00:44, schrieb Andreas Kloeckner:
>>> Michael Biebl <bi...@debian.org> writes:
>>>> Am 17.08.2013 05:42, schrieb Andreas Kloeckner:
>
>>>>> 192.168.1.1:/mnt/main   /mnt/nfs-main           nfs
>>>>> soft,local_lock=all,timeo=30,vers=3     0 0
>>>>> 192.168.1.1:/mnt/aux    /mnt/nfs-aux            nfs
>>>>> soft,local_lock=all,timeo=30,vers=3     0 0
>>>>
>>>> Can you mark the fstab entries with the _netdev mount option and try
>>>> again, please. This should tell systemd to mark the mount point as a
>>>> remote mount.
>>>
>>> Yep, looks like that helped.
>> 
>> Yeah, remote mount points are supposed to be having that _netdev option
>> set. So now I wonder what to do about this bug, close it?
>
> From the relevant man page [1]:
>
> _netdev
> The filesystem resides on a device that requires network access (used to
> prevent the system from attempting to mount these filesystems until the
> network has been enabled on the system).
>
> [1] http://linux.about.com/od/commands/l/blcmdl8_mount.htm

No idea, up to you. Specifying _netdev for an NFS mount feels a bit
redundant. It's also a regression of sorts, since sysvinit appears to
handle this ok.

Andreas

Attachment: pgpIt_K3G7MLF.pgp
Description: PGP signature

Reply via email to