From owner-freebsd-hackers Fri Mar 20 22:45:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01455 for freebsd-hackers-outgoing; Fri, 20 Mar 1998 22:45:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01448 for ; Fri, 20 Mar 1998 22:45:01 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA20146; Sat, 21 Mar 1998 01:45:05 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803210645.BAA20146@dyson.iquest.net> Subject: Re: inetd in realloc():warning:junk pointer, towo low to make sense. In-Reply-To: <199803210625.WAA00813@monk.via.net> from Joe McGuckin at "Mar 20, 98 10:25:25 pm" To: joe@via.net (Joe McGuckin) Date: Sat, 21 Mar 1998 01:45:04 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What causes this? It seems to unrecoverable. Inetd must be restarted > by hand. > I have seen the problem when running a buggered version of -current. If you are running a current between 13-mar and 20-mar, you could be hosing your filesystems. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message