From owner-freebsd-current Sun Jul 5 22:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07934 for freebsd-current-outgoing; Sun, 5 Jul 1998 22:56:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07927 for ; Sun, 5 Jul 1998 22:56:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id HAA11052; Mon, 6 Jul 1998 07:53:04 +0200 (CEST) To: Greg Lehey cc: rotel@indigo.ie, Bill Paul , Kris Kennaway , current@FreeBSD.ORG Subject: Re: inetd problems In-reply-to: Your message of "Mon, 06 Jul 1998 11:13:01 +0930." <19980706111301.V18970@freebie.lemis.com> Date: Mon, 06 Jul 1998 07:53:01 +0200 Message-ID: <11050.899704381@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980706111301.V18970@freebie.lemis.com>, Greg Lehey writes: >> 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. well, lets just say that under some bizarre circumstances this happens too fast, ok ? :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message