Bug#551821: initscripts: fails to mount NFS shares at boot

2012-07-27 Thread Christoph Pleger
I have the same problem and neither setting ASYNCMOUNTNFS=no in
/etc/default/rcS nor using bg as a mount option in /etc/fstab solves it.

Both of these lead to the following error message, though my server name
really exists:

mount.nfs: Failed to resolve server server-name: Name or service not known

When I change the name to the corresponding IP address, the error is "No
route to host".

It seems that the network is not really up yet when
/etc/network/if-up.d/mountnfs is executed.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/40294.129.217.24.151.1343392278.squir...@postamt.cs.uni-dortmund.de



Bug#551821: initscripts: fails to mount NFS shares at boot

2011-09-13 Thread Dagobert
Hi,

this is the same Bug as #485659.

It is probably not really a bug but poorly documented.

1. If you use NFS Root or required NFS shares you are supposed to use the 
following anyway:

/etc/default/rcS

ASYNCMOUNTNFS=no

This solves also the mount at boot time of more unimportant shares

2. For unimportant/not system required NFS shares you should use the option 
"bg" in the fstab





Regards



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1301076156.2197.1315982295227.JavaMail.root@zm0