From owner-freebsd-hackers  Thu Apr 13 17:17:41 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id RAA02701
          for hackers-outgoing; Thu, 13 Apr 1995 17:17:41 -0700
Received: from ain.charm.net (ain.charm.net [198.69.35.206])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA02695
          ; Thu, 13 Apr 1995 17:17:38 -0700
Received: (from nc@localhost) by ain.charm.net (8.6.11/8.6.9) id UAA07580; Thu, 13 Apr 1995 20:11:38 -0400
Date: Thu, 13 Apr 1995 20:11:38 -0400 (EDT)
From: Network Coordinator <nc@ain.charm.net>
To: freebsd-hackers@FreeBSD.org, freebsd-questions@FreeBSD.org
Subject: Processes not dying!
Message-ID: <Pine.BSF.3.91.950413200452.7562A-100000@ain.charm.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@FreeBSD.org
Precedence: bulk


I am running a February Snapshot, and occassionally get these processes 
that just decide not to die. cp does it, find and a number of other 
programs. They don't even have to be backgrounded to die in a way kill -9 
won't help. I *can* kill the controlling shell with a kill -9 from 
another terminal, but these processes stay on record. (rebooting actually 
works, but is not practical on a regular basis)

Any ideas or suggestions? The configuration seems otherwise quite stable. 

Thanks,

-Jerry.