From owner-freebsd-questions Thu Nov 19 09:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26557 for freebsd-questions-outgoing; Thu, 19 Nov 1998 09:42:27 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26546 for ; Thu, 19 Nov 1998 09:42:25 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA19561; Thu, 19 Nov 1998 09:41:50 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 19 Nov 1998 09:41:49 -0800 (PST) From: Doug White To: Jordan Krushen cc: freebsd-questions@FreeBSD.ORG Subject: Re: rpc.lockd In-Reply-To: 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 On Wed, 18 Nov 1998, Jordan Krushen wrote: > I've noticed in rc.conf that lockd is 'broken', and in reading the man > pages, I'm told that it's only broken when the NFS client is a FreeBSD box > as well. What I have is a scenario where a windows app (which uses > file/record locking across its filesystem) exists at two remote locations, > and we have a FreeBSD box at each site. I was thinking of mounting each > other's filesystems with NFS and then sharing those with Samba, but I take > it the locking won't work correctly. Would simply running a Windows NFS > client on the workstations, running through the BSD gateway, solve the > problem? Any sort of file locking on NFS should not be depended on. There is no documented standard for handling the protocol. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message