From owner-freebsd-bugs Sun Jan 13 8:40:51 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CD61D37B41C; Sun, 13 Jan 2002 08:40:47 -0800 (PST) Received: (from iedowse@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0DGcua32461; Sun, 13 Jan 2002 08:38:56 -0800 (PST) (envelope-from iedowse) Date: Sun, 13 Jan 2002 08:38:56 -0800 (PST) From: Message-Id: <200201131638.g0DGcua32461@freefall.freebsd.org> To: B.Candler@pobox.com, iedowse@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: conf/27408: rc.network hangs at rpc.umntall if stale NFS mounts exist in /var/db/mounttab Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: rc.network hangs at rpc.umntall if stale NFS mounts exist in /var/db/mounttab State-Changed-From-To: open->feedback State-Changed-By: iedowse State-Changed-When: Sun Jan 13 08:05:41 PST 2002 State-Changed-Why: There were a number of bugs in rpc.umntall that have been fixed recently, including a bug that prevented you from simply hitting ^C to let the boot process continue, and old entries weren't expired aas they should be. There are short timeouts set, but RPC calls require portmap lookups, and these seem to wait up to 60 seconds for a reply by default, so your machines probably would have booted after a delay of a few minutes. Is the corrected entry expiration and the ability to interrupt rpc.umntall an acceptable solution to this? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27408 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message