On Mon Aug 27 13:04:38 EDT 2012, cinap_len...@gmx.de wrote:
> small additional note. RFPROC|RFNOMNT alone makes no difference
> of course as parent and child will share the same pgrp. but
> with RFNAMEG or RFCNAMEG it makes a difference.
>
> the number of programs that use this combination is prob
small additional note. RFPROC|RFNOMNT alone makes no difference
of course as parent and child will share the same pgrp. but
with RFNAMEG or RFCNAMEG it makes a difference.
the number of programs that use this combination is probably
very small. it was triggered with irc7 which is not part of
the p
aiju found a bug in port/sysproc.c sysrfork(). in the
RFPROC|RFNOMNT case, it sets up->pgrp->noattach
instead of p->pgrp->noattach setting the *parents*
noattach flag instead of the childs pgrp.
http://code.google.com/p/plan9front/source/detail?r=7bbd45940626e92d4caf11620423a96a3fdc58ad
--
cinap
