reopen 433119 ! thanks
Here the bug is still present, I have up-to-date nfs-common, during bootup the system complains about a not running statd, nfs mounts fail. I am very bad at reading more complex initscripts. I tried but I don't get /etc/init.d/nfs-common when it should do what and why it breaks here. //one fstab nfs entry $ grep pub_eu /etc/fstab 192.168.0.1:/pub/ /mnt/pub_europa nfs timeo=14,intr,rsize=8192,wsize=8192,auto,bg //order of the init scripts $ ls /etc/rcS.d/S4*|egrep "nfs|portmap" /etc/rcS.d/S43portmap /etc/rcS.d/S44nfs-common /etc/rcS.d/S45mountnfs.sh /etc/rcS.d/S46mountnfs-bootclean.sh //current nfs-common installed $ apt-show-versions nfs-common nfs-common/sid uptodate 1:1.1.0-11 //just in case... the md5sum of the skript $ md5sum /etc/init.d/nfs-common 8abcfd5f7e474936eb24e9f1777b2fc3 /etc/init.d/nfs-common //what actually happens at bootup, statd is started too late $ grep statd /var/log/boot Sun Jul 22 13:48:21 2007: mount.nfs: rpc.statd is not running but is required for remote locking Sun Jul 22 13:48:21 2007: Either use "-o nolocks" to keep locks local, or start statd. Sun Jul 22 13:48:21 2007: mount.nfs: rpc.statd is not running but is required for remote locking Sun Jul 22 13:48:21 2007: Either use "-o nolocks" to keep locks local, or start statd. Sun Jul 22 13:48:21 2007: mount.nfs: rpc.statd is not running but is required for remote locking Sun Jul 22 13:48:21 2007: Either use "-o nolocks" to keep locks local, or start statd. Sun Jul 22 13:48:23 2007: Starting NFS common utilities: statd idmapd. Sun Jul 22 13:48:39 2007: Starting NFS common utilities: statd idmapd. greets Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
