From owner-freebsd-bugs Mon Dec 13 6:20: 5 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 156B2150DA for ; Mon, 13 Dec 1999 06:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id GAA25824; Mon, 13 Dec 1999 06:20:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Mon, 13 Dec 1999 06:20:03 -0800 (PST) Message-Id: <199912131420.GAA25824@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: emmanuel dupont Subject: Re: misc/15457: inetd makes FreeBSD crash Reply-To: emmanuel dupont Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/15457; it has been noted by GNATS. From: emmanuel dupont To: freebsd-gnats-submit@freebsd.org, emmanuel.dupont@alcatel.fr Cc: Subject: Re: misc/15457: inetd makes FreeBSD crash Date: Mon, 13 Dec 1999 15:10:35 +0100 I made a mistake, the problem is not inetd. It's a null-fs one. I did a "mount_null /home/tmp /tmp" ( my / was full ). I and i changed the fstab too. It worked fine (seems to) but it hang with the script "/tmp/prox.sh", inetd is not guilty. Reading the "man page" i see that null-fs was buggy so i think you can close this call. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message