From owner-freebsd-chat  Mon Nov 10 11:38:44 1997
Return-Path: <owner-freebsd-chat>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA22993
          for chat-outgoing; Mon, 10 Nov 1997 11:38:44 -0800 (PST)
          (envelope-from owner-freebsd-chat)
Received: from terror.hungry.com (fn@terror.hungry.com [169.131.1.215])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA22988
          for <freebsd-chat@freebsd.org>; Mon, 10 Nov 1997 11:38:42 -0800 (PST)
          (envelope-from fn@LISP-READER.Hungry.COM)
Received: (from fn@localhost)
	by terror.hungry.com (8.8.7/8.8.7) id LAA11943;
	Mon, 10 Nov 1997 11:38:40 -0800 (PST)
To: freebsd-chat@freebsd.org
Subject: Re: Crashing FreeBSD
References: <Pine.BSF.3.91.971110193644.4123A-100000@gatekeeper.barcode.co.il>
	<Pine.OSF.3.96.971110104336.8311A-100000@titan.mcit.com>
From: Faried Nawaz <fn@LISP-READER.Hungry.COM>
Date: 10 Nov 1997 11:38:39 -0800
In-Reply-To: ttraylor@titan.mcit.com's message of 10 Nov 1997 10:45:20 -0800
Message-ID: <lwk9egbku8.fsf@terror.hungry.com>
Lines: 7
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-freebsd-chat@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

ttraylor@titan.mcit.com (Thomas S. Traylor) writes:

  A reboot was the only real way to clean it up. There were to many
  process to kill off.  Everytime you killed off a process, it allowed
  another process for that user to startup. 

Judicious use of kill -STOP will help here.