Re: Terminating Child process Dynamically

2012-03-07 Thread Torsten Förtsch
On Friday, 02 March 2012 13:49:34 Perrin Harkins wrote: You can use $r--child_terminate(). 2 remarks: 1) you can use this method at any point in the request cycle. It marks the process to be terminated when the current request is done. 2) the way child_terminate() exits is quite nasty because

Re: Terminating Child process Dynamically

2012-03-07 Thread Perrin Harkins
- Perrin On Mar 7, 2012 7:00 AM, Torsten Förtsch torsten.foert...@gmx.net wrote: On Friday, 02 March 2012 13:49:34 Perrin Harkins wrote: You can use $r--child_terminate(). 2 remarks: 1) you can use this method at any point in the request cycle. It marks the process to be terminated when

Re: Terminating Child process Dynamically

2012-03-07 Thread Torsten Förtsch
On Wednesday, 07 March 2012 08:06:37 Perrin Harkins wrote: It doesn't call perl_destruct()? I thought it did in mod_perl 1 Yes, in mp1 it did. Not so in mp2. static apr_status_t child_terminate(void *data) { apr_pool_t *pool = (apr_pool_t *)data; /* On the first pass, re-register so

Re: Terminating Child process Dynamically

2012-03-07 Thread Perrin Harkins
2012/3/7 Torsten Förtsch torsten.foert...@gmx.net: Yes, in mp1 it did. Not so in mp2. Oh, I see this was covered on the dev list. It doesn't call perl_destruct() because it may be running under threads, which mp1 didn't need to worry about. - Perrin

Re: Terminating Child process Dynamically (and keeping huge amounts of data in RAM)

2012-03-03 Thread Randolf Richardson
Bouncing means restart the application to bring the current changes and new data to the cache. We can't use the following logic as there are huge number of existing data cache and perl modules involved. So the changes will be massive. Keeping code in RAM is fine (that's one of the

Terminating Child process Dynamically

2012-03-02 Thread Shibi Ns
I would like terminate current sever Child process after the end of current request because some data is cached and data is changed after the process creation. The data cached during InitChild phase Is it possible ? Which phase should i do this -- --Shibi Ns--

Re: Terminating Child process Dynamically

2012-03-02 Thread André Warnier
Shibi Ns wrote: I would like terminate current sever Child process after the end of current request because some data is cached and data is changed after the process creation. The data cached during InitChild phase Is it possible ? It is certainly possible (*), but really, really, really

Re: Terminating Child process Dynamically

2012-03-02 Thread Perrin Harkins
On Fri, Mar 2, 2012 at 3:20 AM, Shibi Ns shibi...@gmail.com wrote: I would like terminate current sever Child  process after the end of current request because some data is cached and data is changed after the process creation.  The data cached during InitChild phase Is it possible ? It

Re: Terminating Child process Dynamically

2012-03-02 Thread Shibi Ns
Bouncing means restart the application to bring the current changes and new data to the cache. We can't use the following logic as there are huge number of existing data cache and perl modules involved. So the changes will be massive. Shibi On Fri, Mar 2, 2012 at 4:51 PM, André Warnier

Re: Terminating Child process Dynamically

2012-03-02 Thread Dave Hodgkinson
On 2 Mar 2012, at 19:04, Shibi Ns wrote: Bouncing means restart the application to bring the current changes and new data to the cache. We can't use the following logic as there are huge number of existing data cache and perl modules involved. So the changes will be massive. Shibi