Date: Mon, 18 Nov 2002 23:53:35 +0100 (CET) From: Martijn Pronk <martijn@smartie.xs4all.nl> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/45461: rpc.lockd silently dies when rpc.statd is unavailable Message-ID: <200211182253.gAIMrZfO099389@obelix.in-10.sillywalks.org>
next in thread | raw e-mail | index | archive | help
>Number: 45461
>Category: bin
>Synopsis: rpc.lockd silently dies when rpc.statd is unavailable
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Nov 18 15:00:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Martijn Pronk
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD boekje 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Fri Nov 15 03:55:11
CET 2002 martijn@boekje:/home/obj/home/src/sys/BOEKJE i386
>Description:
While trying to do some testing with lockd, on a machine
that normally does not run lockd + statd, I had some trouble
testing locking over NFS. I could start rpc.lockd, but it
immeadiately stops running. After some retries and manual page
reading I started looking at the code. The code registers some
rpc ports, does a fork and then tries to connect to the local
rpc.statd. If it can't connect to statd it exits whithout logging
anything.
The manpage does mention that rpc.lockd is commonly
used in conjunction with rpc.statd, but not that it's absolutely
required.
If rpc.lockd is enabled from rc.conf this problem is not visible,
the rc scripts do the dependancies correctly.
>How-To-Repeat:
Start rpc.lockd while rpc.statd is not running.
>Fix:
One of the following options:
1. Document the current behaviour in the manualpage
2. Let the program shout loudly about the missing rpc.statd
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211182253.gAIMrZfO099389>