From owner-freebsd-questions Tue Jul 9 11:27:00 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26367 for questions-outgoing; Tue, 9 Jul 1996 11:27:00 -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 LAA26361 for ; Tue, 9 Jul 1996 11:26:56 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-2) with ESMTP id TAA28415; Tue, 9 Jul 1996 19:26:16 +0100 (BST) To: Robin Melville cc: questions@FreeBSD.ORG From: "Gary Palmer" Subject: Re: 2.1.5 Stable and rpc.lockd In-reply-to: Your message of "Tue, 09 Jul 1996 11:18:16 BST." <199607091018.LAA15174@charlie.nadt.org.uk> Date: Tue, 09 Jul 1996 19:26:14 +0100 Message-ID: <28413.836936774@palmer.demon.co.uk> Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Robin Melville wrote in message ID <199607091018.LAA15174@charlie.nadt.org.uk>: > We've now turned our whole site over to FreeBSD and are delighted > with it. We use our FreeBSD hosts for NFS, email, in-house database > applications, and an HTTP "intranet" and development area for our > external web presence. Because this is a clinical organisation it's > important we have good availability, so we have opted to await your > official releases rather than tracking ongoing work. > Our question is about 2.1.5 RELEASE versus the imminent(?) 2.2 > RELEASE. There is nothing imminent about 2.2, apart from that it'll happen (eventually :-) ). 2.2 is due out about the end of the year. > We understand from several correspondents that a working version of > rpc.lockd is under development on the -current branch. Obviously > this is of importance to us given our NFS requirement. > Does the -stable release contain the rpc.lockd implementation, or should we > wait for 2.2? If you want rpc.lockd (and I'm not sure WHY you want it, nothing you said above about what you use FreeBSD for, apart from e-mail, really needs rpc.lockd, and if you are NFS mounting /var/mail, you're also asking for trouble :-( ) then youy will likely have to wait for 2.2-RELEASE, and even then I can't guarentee that a fully functional rpc.lockd will be present. Currently, I believe, a stub rpc.lockd is in the code, which just blindly accepts all lock requests without actually doing anything about checking to see if it just granted multiple clients with locks on a single file. It's mainly to quieten DOS based NFS clients which insist on talking to a lockd server. Considering that people (in the know) say that Sun never got rpc.lockd right either, I'd be surprised if we get WORKING NFS locking which also inter-operates with Sun code properly. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info