On Sun, 15 Jul 2007 the mental interface of Steinar H. Gunderson told: > On Sun, Jul 15, 2007 at 02:06:21PM +0200, Elimar Riesebieter wrote: > > rpc.statd is not running but is required for remote locking > > Either use "-o nolocks" to keep locks local, or start statd. > > > > --- mountnfs.orig 2007-07-13 12:01:18.000000000 +0200 > > +++ mountnfs 2007-07-15 13:38:21.000000000 +0200 > > @@ -109,7 +109,7 @@ > > # rpc.idmapd, and loads the right kernel modules if > > # applicable) if we use Kerberos and/or NFSv4 mounts. > > # > > - if [ "$gss_or_idmap" = yes ] && [ -x /etc/init.d/nfs-common ] > > + if [ -x /etc/init.d/nfs-common ] > > then > > /etc/init.d/nfs-common start > > fi > > > > works. > > Well, we can't start it unconditionally. With my patch applied, could you > please add an "echo $start_nfs" before the if, and report the output? I'm > wondering if nfs-common refuses to start due to portmap, or if something else > is going on.
..... DHCPACK from 192.168.200.1 bound to 192.168.200.202 -- renewal in 12327 seconds. yes Starting NFS common utilities: statd. mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd. done. Starting portmap daemon.... ..... Elimar -- Experience is something you don't get until just after you need it!
signature.asc
Description: Digital signature
