From owner-freebsd-current  Sun Nov  8 13:37:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA24870
          for freebsd-current-outgoing; Sun, 8 Nov 1998 13:37:05 -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 NAA24851
          for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 13:37:01 -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 QAA18829;
	Sun, 8 Nov 1998 16:36:26 -0500 (EST)
Date: Sun, 8 Nov 1998 16:36:26 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Eivind Eklund <eivind@yes.no>
cc: dg@root.com, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108171319.19261@follo.net>
Message-ID: <Pine.BSF.4.05.9811081628170.482-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 8 Nov 1998, Eivind Eklund wrote:

> On Sun, Nov 08, 1998 at 04:50:23PM +0100, Eivind Eklund wrote:
> > On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> > > If the application (phk malloc or the caller of malloc?) isn't
> > > prepared for this, it may end up with a NULL pointer that it doesn't
> > > expect - perhaps not even tripping over it until sometime later.
> > 
> > I'm pretty sure this is not the problem.  Inactive daemons seems start
> > dying, and I don't always get the "out of swap space" message that
> > comes with setting swap_pager_full.
> 
> Oh, and another aspect: This suddenly started happening.  It has been
> stable for 3/4 of a year, and then suddenly started happening
> reproducably one day, after a kernel update while John was doing his
> changes.

I'd never seen this until I went from 2.2.7 to 3.0-BETA and later
-RELEASE.  When I made the move, there were no hardware or swap
configuration changes.  Apache, compiled under 2.2.7, started
having problems that did not change when I re-compiled under 3.0.
Sendmail and inetd are different in 3.0 so I can't make any
cross-version comparisons there.

So something is different...whether inetd, apache and sendmail
(and some have reported crond) are just having latent bugs
activated by a change in the OS, or the OS is whacky I don't
know.

Anyway, the disk housing my extra 128MB of swap is just a
temporary loaner so I anticipate returning to crashing inetd
soon.  :-)

-john


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message