Date: Thu, 13 Jan 2005 22:26:30 -0500 From: Bruce Campbell <bruce@engmail.uwaterloo.ca> To: freebsd-questions@freebsd.org Cc: Paul McKone <pdmckone@engmail.uwaterloo.ca> Subject: Re: flock failure on NFS from 5.3 client to 4.7 server Message-ID: <1105673190.41e73be6d7349@www.nexusmail.uwaterloo.ca> In-Reply-To: <20050114024656.GA66730@xor.obsecurity.org> References: <1105670575.41e731af8de9a@www.nexusmail.uwaterloo.ca> <20050114024656.GA66730@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Kris Kennaway <kris@obsecurity.org>: > > ... > > After the mail server upgrade to 5.3, flock gives error "operation not supported" > > on nfs mounted home directories. > > ... > > On our NFS server, rpc.statd is running, but rpc.lockd wasn't. Started > > it, still no worky. Killed it, other 4.7 clients still flock fine. > > rpc.lockd needs to be running on *both* client *and* server. > > 4.x gets away with it because the rpc.lockd implementation does not in > fact implement locking on the client. > > Kris > Thanks, that has fixed it, and I've added the appropriate rc.conf settings on the client: rpc_lockd_enable="YES" # Run NFS rpc.lockd needed for client/serv rpc_statd_enable="YES" # Run NFS rpc.statd needed for client/serv rpcbind_enable="YES" # Run the portmapper service and on the server: rpc_lockd_enable="YES" # Run NFS rpc.lockd (*broken!*) if nfs_server. rpc_statd_enable="YES" # Run NFS rpc.statd if nfs_server (or NO). -- Bruce Campbell Engineering Computing CPH-2374B University of Waterloo (519)888-4567 ext 5889 ---------------------------------------- This mail sent through www.mywaterloo.ca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1105673190.41e73be6d7349>