Date: Sun, 16 Jan 2005 00:54:34 +0100 From: Erik Norgaard <norgaard@locolomo.org> To: Bryce Kahle <bwkahle@binary.net> Cc: freebsd-questions@freebsd.org Subject: Re: NFS file locking Message-ID: <41E9AD3A.6050209@locolomo.org> In-Reply-To: <24CF3A7650B276458F0A28E49AF18EBE015FBE@binary.exchange.binary.net> References: <24CF3A7650B276458F0A28E49AF18EBE015FBE@binary.exchange.binary.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bryce Kahle wrote: > I've been researching NFS and its file locking capabilities on FreeBSD > and I can't seem to find the answer to my question, so I thought I would > ask it here. > > In this document > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-post.h > tml#NETWORK-CONFIGURATION-CONT > > It mentions this: > "The next option listed here is the rpc.lockd option, which, when > selected, will provide file locking services. This is usually used with > rpc.statd to monitor what hosts are requesting locks and how frequently > they request them. While these last two options are marvelous for > debugging, they are not required for NFS servers and clients to operate > correctly." > > Is rpc.lockd required for fcntl() style locking to work correctly? NFS in it self does not provide any filelocking mechanisms. Your only option is to rely on lockd. lockd needs statd to start correctly. I think that lockd makes filelocking work among other nfs clients but I don't know if the server will respect this kind of filelocking or if it is interpreted as fcntl style locking. I hope this answers half your question :-) cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E9AD3A.6050209>