rfork problem
Igor Serikov
bt at turtle.freedns.us
Tue Nov 4 01:11:35 PST 2003
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.
>
>
More information about the freebsd-hackers
mailing list