From owner-freebsd-hackers  Tue Jun 10 19:20:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA22029
          for hackers-outgoing; Tue, 10 Jun 1997 19:20:40 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA21984
          for <hackers@freebsd.org>; Tue, 10 Jun 1997 19:20:25 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id TAA01646
	for <hackers@freebsd.org>; Tue, 10 Jun 1997 19:04:53 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd001644; Wed Jun 11 02:04:50 1997
Message-ID: <339E0785.2781E494@whistle.com>
Date: Tue, 10 Jun 1997 19:03:49 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: BSD2.2 (a while ago) and ppwait state
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Does anyone know why we are seeing this on a machine
with kernels several months old?
I don't remember discussion of this..

basically, processes start freezing (after 6 hours)
in 'ppwait' state, which appears to be related to vfork.
I thought I'd ask forst before doing tins of research
on the topic.

julian