From owner-freebsd-current  Sun Apr 13 17:47:05 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA05009
          for current-outgoing; Sun, 13 Apr 1997 17:47:05 -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 RAA05003
          for <current@freebsd.org>; Sun, 13 Apr 1997 17:47:00 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id TAA12699 for current@freebsd.org; Sun, 13 Apr 1997 19:46:58 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199704140046.TAA12699@dyson.iquest.net>
Subject: Potential solution to problems with -current
To: current@freebsd.org
Date: Sun, 13 Apr 1997 19:46:58 -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

If you are having problems with -current, try the following patch
to kern_fork.c.  If I get positive responses, and you are running
absolutely the latest cvs code, then I'll put this mod in until
I can find out what is wrong:


*** kern_fork.c	Sat Apr 12 20:48:24 1997
--- kern_fork.c.nv	Sun Apr 13 19:45:30 1997
***************
*** 99,103 ****
  	int retval[];
  {
! 	return (fork1(p, (RFFDG|RFPROC|RFPPWAIT|RFMEM), retval));
  }
  
--- 99,103 ----
  	int retval[];
  {
! 	return (fork1(p, (RFFDG|RFPROC|RFPPWAIT), retval));
  }