From owner-freebsd-stable Fri Nov 10 5:56:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 50EA237B479 for ; Fri, 10 Nov 2000 05:56:40 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id FAA06024; Fri, 10 Nov 2000 05:56:27 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda06022; Fri Nov 10 05:56:26 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.1/8.9.1) id eAADuPi07049; Fri, 10 Nov 2000 05:56:25 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdXQ7047; Fri Nov 10 05:55:34 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.1/8.9.1) id eAADtWf68318; Fri, 10 Nov 2000 05:55:32 -0800 (PST) Message-Id: <200011101355.eAADtWf68318@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdb68314; Fri Nov 10 05:55:29 2000 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.1.1-RELEASE X-Sender: cy To: Erik Trulsson Cc: cam , stable@FreeBSD.ORG Subject: Re: rpc.lockd broken in FreeBSD NFS In-reply-to: Your message of "Wed, 08 Nov 2000 17:45:21 +0100." <20001108174521.A16846@student.uu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Nov 2000 05:55:29 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001108174521.A16846@student.uu.se>, Erik Trulsson writes: > On Wed, Nov 08, 2000 at 02:53:47PM +0100, cam wrote: > > hi > > > > I have to use rpc.lockd on my NFS server (FreeBSD 4.0-STABLE) and I've noti > ce that it is broken with this line in /etc/defaults/rc.conf: > > > > 113: rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if > nfs_server. > > > > 1/ Why is it broken ? I've search in the archives but I've not found any go > od answers. > > You can't have looked that hard. This question did come up earlier this > year on -questions and it wasn't difficult to find the answer searching > through the list-archives. > > Anyway, the answer is that lockd is just a dummy implementation. When the > client requests a lock rpc.lockd will just say "A lock? Sure, here you have > one." without actually locking anything. > > The only reason for running this is when you have semi-broken clients > (usually DOS/Windows based) that insist on getting a lock even though they > don't really need it. Then lockd will make them work. That's because MS systems lock every file that is opened, local and remote, with either a shared or exclusive lock. Interestingly, coupled with an Oracle bug, one can trick Oracle into thinking a database is corrupt without actually touching a byte in the database using this "feature" of MS operating systems by running a backup (Veritas or Legato) just prior to starting Oracle. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message