Date: Thu, 19 Nov 1998 10:31:05 -0800 (PST) From: Jordan Krushen <wired@purplemedia.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: rpc.lockd Message-ID: <Pine.BSF.3.96.981119103053.23395A-100000@pc-37001.bc.rogers.wave.ca> In-Reply-To: <Pine.BSF.4.03.9811190941060.2017-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, then can someone point me to a better solution? ;) On Thu, 19 Nov 1998, Doug White wrote: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981119103053.23395A-100000>