From owner-freebsd-questions Wed Mar 22 8:58:26 2000 Delivered-To: freebsd-questions@freebsd.org Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (Postfix) with ESMTP id 1984F37BD9B; Wed, 22 Mar 2000 08:58:22 -0800 (PST) (envelope-from shovey@buffnet.net) Received: from buffnet11.buffnet.net (buffnet11.buffnet.net [205.246.19.55]) by buffnet4.buffnet.net (8.9.3/8.8.7) with ESMTP id LAA27370; Wed, 22 Mar 2000 11:56:31 -0500 (EST) (envelope-from shovey@buffnet.net) Date: Wed, 22 Mar 2000 11:56:24 -0500 (EST) From: Steve Hovey To: Erik Trulsson Cc: Grigory Kljuchnikov , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: errno (46) - for FreeBSD 4.0 NFS server In-Reply-To: <20000322175118.A901@student.csd.uu.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe the lockd daemon is used in environments where applications at the client end will not work unless they can make a lock call and get a positive result.. so in environments where you feel its fairly safe to fake a lock to a client app, in order to get the app working at all, that you would use this. (At least I think that used to be the reason for it) On Wed, 22 Mar 2000, Erik Trulsson wrote: > On Wed, Mar 22, 2000 at 03:46:12PM +0300, Grigory Kljuchnikov wrote: > > Thank you, Erik! > > > > I find rpc.lockd and start it manually. My test with NFS locking works right. > > But it don't start on boot by default if I enable NFS server in > > /stand/sysinstall and there is the comment in /etc/default/rc.conf > > for rpc_lockd_enable: > > > > rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. > > > > Does the comment "(*broken!*)" mean that rpc.lockd doesn't work properly? > > > > To be honest I don't know. I haven't used it myself but only read the > manpages. (Since I only use NFS between FreeBSD boxes and they don't support > client-side locking it seems pointless to have it on the server.) > > That comment does seem to imply that something is broken but then the > manpage really should say something about that. (This might of course > indicate that the manpage isn't in sync with reality.) > > Somebody who knows what is up with rpc.lockd is welcome to comment. > > > > > > On Wed, 22 Mar 2000, Erik Trulsson wrote: > > > > > On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote: > > > > Thierry, thank you for the information, > > > > but it's very bad that there isn't NFS locking in FreeBSD. > > > > I'm afraid I need to move my FreeBSD NFS server to Solaris > > > > for x86. > > > > > > > > I don't understand why NFS locking isn't in FreeBSD. > > > > Is it difficult in the implementation or are there another > > > > global problems in the kernel (or in the native filesystem)? > > > > > > > > Who know when the NFS locking is planed to release in FreeBSD? > > > > > > > > > > > > > > > > > Actually I think that server side locking *is* implemented but client side > > > locking isn't. > > > 'man 8 rpc.lockd' for more information. > > > (And 'man 5 rc.conf' for information on how to start it at bootup. > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message