From owner-freebsd-hackers Sun Jun 25 18:34:03 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA15636 for hackers-outgoing; Sun, 25 Jun 1995 18:34:03 -0700 Received: from eldorado.net-tel.co.uk (eldorado.net-tel.co.uk [193.122.171.253]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA15630 for ; Sun, 25 Jun 1995 18:33:58 -0700 From: Andrew.Gordon@net-tel.co.uk Received: (from root@localhost) by eldorado.net-tel.co.uk (8.6.12/8.6.10) id CAA17097 for hackers@freebsd.org; Mon, 26 Jun 1995 02:33:23 +0100 X400-Received: by mta "eldorado" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 26 Jun 95 2:33:13 +0100 X400-Received: by mta "net-tel cambridge" in "/PRMD=net-tel/ADMD=gold 400/C=gb/"; Relayed; Mon, 26 Jun 95 1:33:11 +0000 X400-Received: by "/PRMD=Net-Tel/ADMD=Gold 400/C=GB/"; Relayed; Mon, 26 Jun 95 2:32:12 +0100 X400-MTS-Identifier: ["/PRMD=Net-Tel/ADMD=Gold 400/C=GB/";monorail:7738-950626013212-BA25] X400-Content-Type: P2-1984 (2) X400-Originator: Andrew.Gordon@net-tel.co.uk Original-Encoded-Information-Types: IA5-Text X400-Recipients: hackers@freebsd.org Date: Mon, 26 Jun 95 2:32:12 +0100 Content-Identifier: NFS file locking Message-Id: <"monorail:7738-950626013212-BA25*/G=Andrew/S=Gordon/O=Net-Tel Computer Systems Ltd/PRMD=NET-TEL/ADMD=Gold 400/C=GB/"@MHS> To: hackers@freebsd.org Subject: NFS file locking Sender: hackers-owner@freebsd.org Precedence: bulk I just installed a new FreeBSD box to replace our old (slowly dying) NFS fileserver. Unfortunately, I discover that FreeBSD does not have rpc.statd nor rpc.lockd - which didn't matter as a client, but causes indigestion to our other clients when FreeBSD is used as a server: Jun 26 01:51:31 hst rpc.statd[177]: rpc.statd: cannot talk to statd at monorail Jun 26 01:52:16 hst last message repeated 3 times So: 1) Am I right in believing that this stuff doesn't exist in FreeBSD 2.0.5? (seems like it, from looking at previous discussion in the lists archive) 2) Any work-in-progress that I might assist with? Or any previous discussion of how this ought to be implemented in FreeBSD? 3) If not, any pointers to the spec so I can have a go at implementing from scratch? If I can just dummy up the protocol to keep the other machines happy, I would be back in business, and one step on the way to doing the whole job. Any info/ideas greatfully received.... Andrew.