From owner-freebsd-current Sat Oct 26 06:50:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27038 for current-outgoing; Sat, 26 Oct 1996 06:50:35 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA27031 for ; Sat, 26 Oct 1996 06:50:30 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.8.2/8.7.3) id NAA04998; Sat, 26 Oct 1996 13:50:06 GMT Date: Sat, 26 Oct 1996 13:50:06 GMT From: Adam David Message-Id: <199610261350.NAA04998@veda.is> To: wpaul@skynet.ctr.columbia.EDU (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: /etc/rc* stuff Newsgroups: list.freebsd.current References: <199610242315.BAA04473@uriah.heep.sax.de> <199610250014.UAA23879@skynet.ctr.columbia.edu> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > - Even though we have rpc.lockd and rpc.statd in the tree now, there >> > are no knobs for it in /etc/sysconfig or /etc/rc. Shouldn't we be >> > be starting them if NFS is turned on? >> >> You mean, ``just to confuse the people''? :) >> >> Remember, they are no-ops still. >No, they aren't. rpc.statd is fully functional. rpc.lockd is halfway >functional. In either case, it doesn't hurt to have them on. $ man rpc.lockd | vgrep BUGS The current implementation provides only the server side of the protocol (ie. clients running other OS types can establish locks on a FreeBSD fileserver, but there is currently no means for a FreeBSD client to es- tablish locks). $ ^D I'd like to see them in the default /etc/rc too. -- Adam David