testing the Tcl notifier after a fork

[Massimo Manghi <ma...@unipr.it>]

Hi Harald, hi everyone

I want to test the experimental code of Tcl and I need a script that 
uses the Tcl notifier in order to verify it's an equivalent solution for 
preserving the notifier across a fork call. I presume that any 
asynchronous call should provide a valid testbed for this subsystem 
(even an asynchronous read of a file) and I think I don't need to search 
the ::http based script Harald was testing when the problem surfaced, am 
I correct?

  -- Massimo

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

Re: testing the Tcl notifier after a fork

[Harald Oehlmann <ha...@elmicron.de>]

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-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org

Re: testing the Tcl notifier after a fork

[Massimo Manghi <mx...@apache.org>]

Hi

On 09/03/2015 11:02 PM, Harald Oehlmann wrote:
> Hi Massimo,
>
> yes, even an
>
> after 10 "set a 1"
> vwait a
>
> is sufficient.
>

thanks, you grasped the spirit of my request: a conceptual scripts that 
eliminates any redundant complexity and goes straight to the core of the 
problem.

> 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?

cheers

  -- Massimo

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

Re: testing the Tcl notifier after a fork

[Harald Oehlmann <ha...@elmicron.de>]

Hi Massimo,

yes, even an

after 10 "set a 1"
vwait a

is sufficient.

Also check, if an interpreter stops, that another interpreter is stopped
(wrong linked pipes issue, forked interpreter will abort parent insead
itself)

Regards,
Harald

Am 03.09.2015 um 18:50 schrieb Massimo Manghi:
> Hi Harald, hi everyone
> 
> I want to test the experimental code of Tcl and I need a script that
> uses the Tcl notifier in order to verify it's an equivalent solution for
> preserving the notifier across a fork call. I presume that any
> asynchronous call should provide a valid testbed for this subsystem
> (even an asynchronous read of a file) and I think I don't need to search
> the ::http based script Harald was testing when the problem surfaced, am
> I correct?
> 
>  -- Massimo


-- 
ELMICRON Dr. Harald Oehlmann GmbH
Koesener Str. 85
06618 Naumburg
Germany
Phone: +49 (0)3445 78112-0
Fax: +49 (0)3445 78112-19
www.Elmicron.de
German legal references:
Geschaeftsfuehrer: Dr. Harald Oehlmann, Jens Oehlmann
UST Nr. / VAT ID No.: DE206105272
HRB 212803 Stendal

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