From owner-freebsd-current Sun Jul 5 18:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07247 for freebsd-current-outgoing; Sun, 5 Jul 1998 18:45:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07221 for ; Sun, 5 Jul 1998 18:44:42 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.0/8.9.0) id LAA05754; Mon, 6 Jul 1998 11:13:02 +0930 (CST) Message-ID: <19980706111301.V18970@freebie.lemis.com> Date: Mon, 6 Jul 1998 11:13:01 +0930 From: Greg Lehey To: Poul-Henning Kamp , rotel@indigo.ie Cc: Bill Paul , Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems References: <199807052032.VAA04596@indigo.ie> <10403.899676678@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <10403.899676678@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Jul 06, 1998 at 12:11:18AM +0200 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 Monday, 6 July 1998 at 0:11:18 +0200, Poul-Henning Kamp wrote: > In message <199807052032.VAA04596@indigo.ie>, Niall Smart writes: >> On Jul 5, 12:56pm, Bill Paul wrote: >>> Subject: Re: inetd problems >>> >>> I encounter messages like this occasionally with my own code (mostly >>> NIS+ stuff) and without exception, the cause has always been some >>> kind of bug on my part (double free(), free()ing static buffers by >>> mistake, corrupting the heap by wandering past the end of a malloc()ed >>> buffer, etc...). All the theories I've heard so far point to some >>> kind of VM problem; nobody as yet has been willing to admit that >>> the problem is a bug in inetd. >> >> Well, if you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 >> you'll see why, it doesn't look like it's inetd's fault since other >> services fail at the same time. > > There are two problems here, at least as far as my diagnosis goes: > > 1: kernel/VM problem > means that you run out of memory and eventually malloc(3) > may fail. Do you mean kernel/VM problem or resource problem? I don't see a kernel bug, just the probability that all memory gets used up. > 2: inetd probelm > inetd doesn't correctly handle some exception conditions, > maybe related to malloc(3) failing for the above or other > reasons. Agreed. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message