From owner-freebsd-current Sun Jul 5 13:52:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03102 for freebsd-current-outgoing; Sun, 5 Jul 1998 13:52:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (root@ts01-44.waterford.indigo.ie [194.125.139.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03005 for ; Sun, 5 Jul 1998 13:52:25 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id VAA04596; Sun, 5 Jul 1998 21:32:24 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807052032.VAA04596@indigo.ie> Date: Sun, 5 Jul 1998 21:32:21 +0000 In-Reply-To: Bill Paul "Re: inetd problems" (Jul 5, 12:56pm) Reply-To: rotel@indigo.ie X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Bill Paul , kkennawa@physics.adelaide.edu.au (Kris Kennaway) Subject: Re: inetd problems Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message