Am 03.09.2015 um 23:15 schrieb Massimo Manghi:
>> Also check, if an interpreter stops, that another interpreter is stopped
>> (wrong linked pipes issue, forked interpreter will abort parent insead
>> itself)
>>
> 
> I think I don't understand it: by 'stopping' you mean 'exiting' as with
> the 'exit' command?

I am sorry, I don't know neither.

When I worked on the notifier not started bug, it happended, that the
exit of a forked process terminated the original process.

I don't know if you can invoke this by exit or if it is done by the
Apache process management.

Apache just started and stopped processes and this always killed the
original process which stopped tcl mother process...
Anyway.
Sorry, was on business trip, looking to my E-Mails..



Harald

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org

Reply via email to