>mount tried to run /usr/sbin/start-statd and it failed for some reason. >What is in /usr/sbin/start-statd ?? >What happens if you run it directly? >What happens if you just run /usr/sbin/rpc.statd?? root@server:~# find /usr/ -name "start-statd"root@server:~# I don't have it!!! >How is that relevant? > man 8 mount >might help you. I think the above problem is serious and "-o loop" may not help // Naderan *Mahmood; ----- Original Message ----- From: NeilBrown <neilb@xxxxxxx> To: Mahmood Naderan <nt_mahmood@xxxxxxxxx> Cc: nfs <linux-nfs@xxxxxxxxxxxxxxx> Sent: Monday, May 2, 2011 1:05 PM Subject: Re: rpc.statd is not running but is required On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan <nt_mahmood@xxxxxxxxx> wrote: > Hi, > I have setup NFS and I checked every thing with documents and manual. > After the client boots up, it says: > > > mount.nfs: rpc.statd is not running but is required for remote locking. > mount.nfs: Either use '-o nolock' to keep locks local, or start statd. > mountall: mount /opt [1000] terminated with status 32 mount tried to run /usr/sbin/start-statd and it failed for some reason. What is in /usr/sbin/start-statd ?? What happens if you run it directly? What happens if you just run /usr/sbin/rpc.statd?? > > and I can not see the shared folder. > my hosts.allow file contains: > > > portmap: 192.168.1.0/255.255.255.0 > lockd: 192.168.1.0/255.255.255.0 > rqoutad: 192.168.1.0/255.255.255.0 > mountd: 192.168.1.0/255.255.255.0 > > > also /etc/exports contain: > /opt 192.168.1.0/255.255.255.0(rw,no_subtree_check,sync,no_root_squash) > > > Any idea about that? What does '-o loop' mean? How is that relevant? man 8 mount might help you. NeilBrown > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
