Date: Mon, 13 Nov 2006 10:31:20 +0100 (CET) From: Daniel Gerzo <danger@FreeBSD.org> To: FreeBSD-gnats-submit@FreeBSD.org Subject: conf/105465: rc.d/nfslocking is dependent on rpcbind Message-ID: <200611130931.kAD9VKOZ006335@cvsup.sk.freebsd.org> Resent-Message-ID: <200611130940.kAD9e2Cg082791@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 105465 >Category: conf >Synopsis: rc.d/nfslocking is dependent on rpcbind >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 13 09:40:02 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Daniel Gerzo >Release: FreeBSD 6.1-PRERELEASE i386 >Organization: The FreeBSD Project >Environment: System: FreeBSD >Description: It looks to me like the rc.d/nfslocking script is dependent on the rpcbind service. I have been setting up NFS and hit this problem, while trying to get rpc.lockd and rpc.statd running. I have been encoutering the same problem as described at: http://lists.freebsd.org/pipermail/freebsd-questions/2004-December/069022.html >How-To-Repeat: Try to start nfslocking without rpcbind enabled and running >Fix: Modification of rc.d/nfslocking will be needed as well as update of NFS Handbook chapter (I can take care of the latter one). >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611130931.kAD9VKOZ006335>