From owner-freebsd-current  Tue Mar 17 17:30:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA16271
          for freebsd-current-outgoing; Tue, 17 Mar 1998 17:30:26 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16234;
          Tue, 17 Mar 1998 17:30:21 -0800 (PST)
          (envelope-from grog@lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id MAA10097;
	Wed, 18 Mar 1998 12:00:17 +1030 (CST)
Received: (from grog@localhost)
          by freebie.lemis.com (8.8.8/8.8.7) id MAA09198;
          Wed, 18 Mar 1998 12:00:17 +1030 (CST)
          (envelope-from grog)
Message-ID: <19980318120016.31155@freebie.lemis.com>
Date: Wed, 18 Mar 1998 12:00:16 +1030
From: Greg Lehey <grog@lemis.com>
To: dyson@FreeBSD.ORG
Cc: FreeBSD-current@FreeBSD.ORG
Subject: Re: Memory leak in inetd in last week's -current?
References: <19980318084414.07315@freebie.lemis.com> <199803180116.UAA00442@dyson.iquest.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89i
In-Reply-To: <199803180116.UAA00442@dyson.iquest.net>; from John S. Dyson on Tue, Mar 17, 1998 at 08:16:27PM -0500
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 17 March 1998 at 20:16:27 -0500, John S. Dyson wrote:
> Greg Lehey said:
>> I've just discovered that my inetd has been rejecting connections with
>> the following message:
>>
>> $ ftp ftp.lemis.com
>> Connected to freebie.lemis.com.
>> inetd in realloc(): warning: junk pointer, too high to make sense.
>> ftp>
>>
>> I took a ktrace of it happening, if that's of any use, and restarted
>> inetd, which made the problem go away.  Any ideas?
>>
> If you are running a kernel after about Saturday, then it is a kernel
> problem, and immediately you should start running an earlier kernel.

Yes, I saw the file system mass destruction problems, but that was
later.  This kernel was built last Thursday (our time), or Wednesday
your time.  Any danger there?

Greg

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