From owner-freebsd-current Sat Nov 7 06:55:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08718 for freebsd-current-outgoing; Sat, 7 Nov 1998 06:55:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08703 for ; Sat, 7 Nov 1998 06:55:06 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA20657; Sat, 7 Nov 1998 09:54:44 -0500 (EST) Date: Sat, 7 Nov 1998 09:54:44 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alexander Litvin cc: current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-Reply-To: <199811071314.PAA23544@grape.carrier.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll do that right now. I'll tell you if inetd/exim/whatever die. Brian feldman On Sat, 7 Nov 1998, Alexander Litvin wrote: > In article you wrote: > BF> I haven't had this bug. And a 3.0 box at school doesn't have it either... > BF> it's not as common as you think. > > Have you beaten your systems to "swap_pager: out of swap space"? > > My system may run for months without any problem. It's home box > -- 32M RAM + 128M swap, and it is enough for day-to-day operation. > But when I artificially overload it, it easily shows all that > sendmails exiting on signal 11, cron jobs not run, etc. > > BF> Brian Feldman > > --- > Did you know ... > > > > > > > > That no-one ever reads these things? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message