From owner-freebsd-questions Fri Jul 5 12:27:33 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01393 for questions-outgoing; Fri, 5 Jul 1996 12:27:33 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01381 for ; Fri, 5 Jul 1996 12:27:28 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id UAA17395; Fri, 5 Jul 1996 20:27:18 +0100 (BST) To: mike@NetworX.ie cc: FreeBSD Support From: "Gary Palmer" Subject: Re: no rpc.statd and rpc.lockd In-reply-to: Your message of "Fri, 05 Jul 1996 19:49:54 -0000." Date: Fri, 05 Jul 1996 20:27:18 +0100 Message-ID: <17393.836594838@palmer.demon.co.uk> Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Ryan wrote in message ID : > If they don't exist, how is file locking performed? It's not over NFS, as I believe that Sun Microsystems have (a) never clearly published their lockd/statd specs and (b) never really got them working properly themselves. I believe there is basic code to do this in -current, but the lockd is a dummy which just accepts all lock requests blindly and approves them, not doing any actual file locking on the server itself. A full implimentation is being worked on, but may be some time yet. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info