From owner-freebsd-bugs@FreeBSD.ORG  Thu Jan  8 14:28:23 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2709416A4CE; Thu,  8 Jan 2004 14:28:23 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1AAF943D4C; Thu,  8 Jan 2004 14:28:22 -0800 (PST)
	(envelope-from dwmalone@FreeBSD.org)
Received: from freefall.freebsd.org (dwmalone@localhost [127.0.0.1])
	i08MSLFR088215;	Thu, 8 Jan 2004 14:28:21 -0800 (PST)
	(envelope-from dwmalone@freefall.freebsd.org)
Received: (from dwmalone@localhost)
	by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i08MSLka088211;
	Thu, 8 Jan 2004 14:28:21 -0800 (PST)
	(envelope-from dwmalone)
Date: Thu, 8 Jan 2004 14:28:21 -0800 (PST)
From: David Malone <dwmalone@FreeBSD.org>
Message-Id: <200401082228.i08MSLka088211@freefall.freebsd.org>
To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	dwmalone@FreeBSD.org
Subject: Re: bin/60806: inetd hangs on non-existent config files
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2004 22:28:23 -0000

Synopsis: inetd hangs on non-existent config files

Responsible-Changed-From-To: freebsd-bugs->dwmalone
Responsible-Changed-By: dwmalone
Responsible-Changed-When: Thu Jan 8 14:15:40 PST 2004
Responsible-Changed-Why: 
I'll take this PR as inetd is my problem.

I think inetd is actually running and providing no services - I'd
expect that if you create its config file and HUP it, it should
continue happily. It isn't clear to me if this is sensible or not.

I think that the patch, as it stands, would cause inetd to exit if
HUPPed after its config file had been deleted, which is probably
bad. Maybe a patch that checks for the existance of the config file
at start-up?

	David.

http://www.freebsd.org/cgi/query-pr.cgi?pr=60806