From owner-freebsd-current  Sun Apr 13 17:25:38 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA03276
          for current-outgoing; Sun, 13 Apr 1997 17:25:38 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA03271
          for <current@freebsd.org>; Sun, 13 Apr 1997 17:25:29 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id TAA12650 for current@freebsd.org; Sun, 13 Apr 1997 19:25:22 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199704140025.TAA12650@dyson.iquest.net>
Subject: Need help from users of -current
To: current@freebsd.org
Date: Sun, 13 Apr 1997 19:25:22 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Current-crew:

I have had a few reports of problems with vfork in -current.  Would anyone
who has *exactly* a current kernel give me some feedback as to how the
system is working? (CTM might be out of sync -- I made an error in the
initial commit.)   I cannot reproduce the problem, and if it is there,
then maybe I can figure out how to.

Thanks!!!
John