From owner-freebsd-current Fri Nov 6 12:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28949 for freebsd-current-outgoing; Fri, 6 Nov 1998 12:42:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28942 for ; Fri, 6 Nov 1998 12:42:52 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id PAA01565; Fri, 6 Nov 1998 15:42:28 -0500 (EST) Date: Fri, 6 Nov 1998 15:42:28 -0500 (EST) From: John Fieber To: "Jordan K. Hubbard" cc: "David E. Cross" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-Reply-To: <2826.910378788@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Nov 1998, Jordan K. Hubbard wrote: > > If it was happening to everyone as much as it was happening to > > me, I seriously doubt 3.0 would have ever reached release > > status...having inetd die every 6 to 24 hours, httpd and sendmail > > every couple days is pretty intolerable. > > Have you tried that new inetd.c replacement that was posted awhile > back? I'm just wondering if it affects the problem. Yes and it was proven ineffectual inside of about 8 hours. With respect to the inetd patch, it may well be a case of two separate problems that manifest themselves in the same way, so fixing one doesn't necessairly remove the symptom. Since other daemons (sendmail, httpd) exhibit the same symptom, something outside of inetd is likely to be involved. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message