Jeff Miller <[EMAIL PROTECTED]> wrote: > It is possible on our test Solaris 8 system that the original > calling bash shell will set the controlling process of the terminal > to the pid that it originally forked to after the new process had > been created. In this case is not the new bash process. It happens > to do this after the new bash has done it's write but before it has > done it's read, this new process still assumes it is still the > controlling process.
Chet, could the foreground process group be set by the forked child itself, before the exec, instead of by the parent? That would at least eliminate the race condition so the results would be predictable, and I think it would prevent the problem in this case. paul _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
