I heve this service mahmood@server:~$ sudo /etc/init.d/nfs-kernel-server restart * Stopping NFS kernel daemon [ OK ] * Unexporting directories for NFS kernel daemon... [ OK ] * Exporting directories for NFS kernel daemon... [ OK ] * Starting NFS kernel daemon [ OK ] I use debian based linux. Is that what you meant? // Naderan *Mahmood; ----- Original Message ----- From: Dennis Jacobfeuerborn <dennisml@xxxxxxxxxxxx> To: NeilBrown <neilb@xxxxxxx> Cc: Mahmood Naderan <nt_mahmood@xxxxxxxxx>; nfs <linux-nfs@xxxxxxxxxxxxxxx> Sent: Monday, May 2, 2011 2:30 PM Subject: Re: rpc.statd is not running but is required On 05/02/2011 10:35 AM, NeilBrown wrote: > 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?? > Have you tried checking if the /etc/init.d/nfslock service is enabled and running? Regards, Dennis -- 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
