From owner-freebsd-current Fri Nov 6 11:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13523 for freebsd-current-outgoing; Fri, 6 Nov 1998 11:00:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13507 for ; Fri, 6 Nov 1998 11:00:54 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id KAA02829; Fri, 6 Nov 1998 10:59:48 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: John Fieber cc: "David E. Cross" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-reply-to: Your message of "Fri, 06 Nov 1998 13:55:09 EST." Date: Fri, 06 Nov 1998 10:59:48 -0800 Message-ID: <2826.910378788@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. David's looked at this one a bit and he can neither reproduce it nor come up with any good ideas right now as to how to go about fixing it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message