From owner-freebsd-chat Mon May 10 17:49: 0 1999 Delivered-To: freebsd-chat@freebsd.org Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (Postfix) with ESMTP id DF3D615CE4 for ; Mon, 10 May 1999 17:48:53 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.3/8.9.2) id SAA12535; Mon, 10 May 1999 18:42:20 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 10 May 1999 18:42:20 -0500 (CDT) Reply-To: conrads@neosoft.com From: Conrad Sabatier To: Pat Lynch Subject: Re: Stupidity subjects box to *severe* stress test -- FreeBSD passes with flying colors Cc: chat@FreeBSD.ORG Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 10-May-99 Pat Lynch wrote: > I made the same mistake once... running tripwire at 1 am, I ran 60 copies > of tripwire, when I woke up in the morning, and logged in remotely, it > was a little sluggish, and the load was up to 134 or something like > that... > > (ok, a *little* sluggish is an understatement) > > but I was able to kill all the tripwire processes (took me 25 minutes) "killall -9 tripwire" took 25 minutes??? I did a killall on cron, cvsup, make, and had things back to normal in no time. Just try *that* on a Winblows box (of course, the Winblows box would have died a horrible death long before that anyway). FreeBSD never ceases to amaze me, I tell ya. -- Conrad Sabatier Anyone who hates Dogs and Kids Can't be All Bad. -- W. C. Fields To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message