From owner-freebsd-hackers Thu Aug 26 19:30:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 0696E1547D for ; Thu, 26 Aug 1999 19:30:04 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id TAA24049; Thu, 26 Aug 1999 19:27:17 -0700 (PDT) Message-Id: <199908270227.TAA24049@lestat.nas.nasa.gov> To: Terry Lambert Cc: gallatin@cs.duke.edu (Andrew Gallatin), freebsd-hackers@FreeBSD.ORG Subject: Re: undocumented vfork behaviour? Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 26 Aug 1999 19:27:16 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Aug 1999 02:20:52 +0000 (GMT) Terry Lambert wrote: > This is a bug. ...but it's a bug in fork(), too. Not just vfork(). > For other bugs in vfork(), look at the fact that the vacation > program does not correctly deal with messages. ...fwiw, NetBSD fixed the vacation(1) bug and another bug in popen(), both of which manifested themselves when NetBSD got a Real Vfork. ...there's actually a fair amount of code that needs to be checked out and fixed when you have a Real Vfork, exit() vs _exit(), etc. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message