From owner-freebsd-security Mon Apr 12 9:15: 2 1999 Delivered-To: freebsd-security@freebsd.org Received: from eagle.aitken.com (eagle.aitken.com [209.249.97.250]) by hub.freebsd.org (Postfix) with ESMTP id 6D55215585 for ; Mon, 12 Apr 1999 09:14:59 -0700 (PDT) (envelope-from jaitken@aitken.com) Received: (from jaitken@localhost) by eagle.aitken.com (8.9.1a/8.9.1) id MAA01726; Mon, 12 Apr 1999 12:12:37 -0400 From: Jeff Aitken Message-Id: <199904121612.MAA01726@eagle.aitken.com> Subject: Re: inetd problems In-Reply-To: <37120E9B.1AE1FD8D@ukonline.net> from Max Booth at "Apr 12, 1999 04:17:47 pm" To: max@ukonline.net (Max Booth) Date: Mon, 12 Apr 1999 12:12:36 -0400 (EDT) Cc: freebsd-security@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL53 (25)] Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Max Booth writes: > Escape character is '^]'. > inetd in realloc(): warning: junk pointer, too low to make sense. > inetd in free(): warning: junk pointer, too low to make sense. > Connection closed by foreign host. I've seen this before, on a 2.2.6 system. IIRC, the answer from Jordan was that there was a subtle but in inetd (or triggered by inetd) which caused this sort of memory problem. I don't recall whether killing and restarting inetd was enough to "fix" it or if it required a reboot. I'm fairly certain that it didn't represent a security problem. --Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message