Date: Tue, 04 Nov 2003 01:11:31 -0800 From: Igor Serikov <bt@turtle.freedns.us> To: David Schultz <das@FreeBSD.ORG> Cc: FreeBSD Bugs <freebsd-bugs@FreeBSD.ORG> Subject: Re: rfork problem Message-ID: <3FA76D43.1040508@turtle.freedns.us> References: <3FA61A17.70605@turtle.freedns.us> <20031104081800.GA78439@VARK.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David, Is it okay to have a condition that can be created by a mortal user and then cannot be changed by the root? The waiting process cannot be killed and would keep "waiting" till system reboot. I do not think it is a good idea to make ppwait state uninterruptible in any case. As to RFNOWAIT, I believe that the correct behavior is to detach after leaving ppwait. David Schultz wrote: > On Mon, Nov 03, 2003, Igor Serikov wrote: > >> Hello, >> >>Combining flags RFNOWAIT and RFPPWAIT in rfork(2) under 4.6-RELEASE >>makes the parent process sleeping on channel "ppwait" forever. > > > RFPPWAIT tells rfork() to wait for the child to exit, and RFNOWAIT > tells rfork() to detach the child such that it never tells the > parent when it exits. So you're getting exactly what you asked > for, as silly as it may be. > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FA76D43.1040508>