From owner-freebsd-current Sun Jul 5 14:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13050 for freebsd-current-outgoing; Sun, 5 Jul 1998 14:40:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (fullermd@shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13010 for ; Sun, 5 Jul 1998 14:40:28 -0700 (PDT) (envelope-from fullermd@shell.futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id QAA06953; Sun, 5 Jul 1998 16:39:36 -0500 (CDT) Message-ID: <19980705163936.43005@futuresouth.com> Date: Sun, 5 Jul 1998 16:39:36 -0500 From: "Matthew D. Fuller" To: Blaz Zupan Cc: Bill Paul , Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems References: <199807051656.MAA14927@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Blaz Zupan on Sun, Jul 05, 1998 at 07:43:10PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 05, 1998 at 07:43:10PM +0200, Blaz Zupan woke me up to tell me: > > More details would help here: under what conditions does this > > problem occur? Do you see the 'realloc' error all the time, or just > > when the system is heavily loaded? Exactly what smtp server is this? > > How many users does the server handle mail for? Can you debug this > > by recompiling inetd with the Electric Fence library and analyzing > > the crash dump? If not, can you at least provide a recipe for > > duplicating the bug so that someone else can try debugging it? > > I had a stupid router box running 2.2.5 with 4MB RAM (yeah, it's possible) > which has been recently upgraded to 8MB (amazing, isn't it? :) and after > telneting about 5-6 times into the box, the next try I try to telnet in I > get the same message. So I guess the best way to reproduce this bug is > just to run out of memory. Or install a box with little or no ram and > little or no swap and start a couple of bigger processes and then telnet > in a couple of times. Or open up Netscape, load a page with a couple of animated GIF's, and go home for the night. It'll just keep allocating more memory for the gif until it eats everything. No, of course I haven't done this! ;) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message