Mark Blackman wrote:
On 17 Apr 2008, at 07:46, Philippe M. Chiasson wrote:
Mark Blackman wrote:
On 16 Apr 2008, at 10:24, Mark Blackman wrote:
On 16 Apr 2008, at 08:42, Philippe M. Chiasson wrote:
Can you try this simple patch and see if it makes your troubles
go away.
It does indeed have
On 18 Apr 2008, at 09:52, Philippe M. Chiasson wrote:
Mark Blackman wrote:
On 17 Apr 2008, at 07:46, Philippe M. Chiasson wrote:
Mark Blackman wrote:
On 16 Apr 2008, at 10:24, Mark Blackman wrote:
On 16 Apr 2008, at 08:42, Philippe M. Chiasson wrote:
Can you try this simple patch and see if
Mark Blackman wrote:
On 16 Apr 2008, at 10:24, Mark Blackman wrote:
On 16 Apr 2008, at 08:42, Philippe M. Chiasson wrote:
Can you try this simple patch and see if it makes your troubles go
away.
It does indeed have the desired effect of getting $$ reset to the
child pid by the time the
On 17 Apr 2008, at 07:46, Philippe M. Chiasson wrote:
Mark Blackman wrote:
On 16 Apr 2008, at 10:24, Mark Blackman wrote:
On 16 Apr 2008, at 08:42, Philippe M. Chiasson wrote:
Can you try this simple patch and see if it makes your troubles
go away.
It does indeed have the desired effect
Mark Blackman wrote:
On 15 Apr 2008, at 13:51, Mark Blackman wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork
module, surely the
mod_perl code must be doing something like this itself, no?
I'd be grateful to understand mod_perl's response to Perl's
pid caching is, given
On 16 Apr 2008, at 08:42, Philippe M. Chiasson wrote:
Can you try this simple patch and see if it makes your troubles go
away.
It does indeed have the desired effect of getting $$ reset to the
child pid by the time the PerlChildInitHandler handler is called.
- Mark
Untested
Index:
On 16 Apr 2008, at 10:24, Mark Blackman wrote:
On 16 Apr 2008, at 08:42, Philippe M. Chiasson wrote:
Can you try this simple patch and see if it makes your troubles go
away.
It does indeed have the desired effect of getting $$ reset to the
child pid by the time the PerlChildInitHandler
On Tue, Apr 15, 2008 at 8:51 AM, Mark Blackman [EMAIL PROTECTED] wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork module,
surely the
mod_perl code must be doing something like this itself, no?
I've been using fork, mod_perl, and $$ for years without a single
problem. Did
While I did find Torsten Förtsch's very useful Perl::AfterFork
module, surely the
mod_perl code must be doing something like this itself, no?
I'd be grateful to understand mod_perl's response to Perl's
pid caching is, given that forking *will* happen in the mod_perl
environment.
- Mark
On 15 Apr 2008, at 13:59, Perrin Harkins wrote:
On Tue, Apr 15, 2008 at 8:51 AM, Mark Blackman [EMAIL PROTECTED]
wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork
module,
surely the
mod_perl code must be doing something like this itself, no?
I've been using fork,
On Tue, Apr 15, 2008 at 9:05 AM, Mark Blackman [EMAIL PROTECTED] wrote:
My assumption is that perl caches the PID on startup and
only reinitializes on perl fork(), thus in the embedded case
a fork() outside the perl API doesn't reinitialize $$ at least
for some cases.
It must be a
On 15 Apr 2008, at 14:15, Perrin Harkins wrote:
On Tue, Apr 15, 2008 at 9:05 AM, Mark Blackman [EMAIL PROTECTED]
wrote:
My assumption is that perl caches the PID on startup and
only reinitializes on perl fork(), thus in the embedded case
a fork() outside the perl API doesn't reinitialize
On Tue 15 Apr 2008, Mark Blackman wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork
module, surely the
mod_perl code must be doing something like this itself, no?
I'd be grateful to understand mod_perl's response to Perl's
pid caching is, given that forking *will*
On 15 Apr 2008, at 16:00, Torsten Foertsch wrote:
On Tue 15 Apr 2008, Mark Blackman wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork
module, surely the
mod_perl code must be doing something like this itself, no?
I'd be grateful to understand mod_perl's response to Perl's
On 15 Apr 2008, at 16:24, Mark Blackman wrote:
On 15 Apr 2008, at 16:00, Torsten Foertsch wrote:
On Tue 15 Apr 2008, Mark Blackman wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork
module, surely the
mod_perl code must be doing something like this itself, no?
I'd be
On Tue, Apr 15, 2008 at 11:00 AM, Torsten Foertsch
[EMAIL PROTECTED] wrote:
There was/is a problem in mp1 that it did/does not reinitialize $$ and
getppid().
Under what circumstances? I use $$ all the time and have never seen
any sort of caching behavior from it. I use Linux.
- Perrin
On Tue 15 Apr 2008, Mark Blackman wrote:
int main(int argc, char *argv){
fork();
printf(my pid is %d\n,getpid());
}
Please use the fork-syscall here not the C function.
Torsten
--
Need professional mod_perl support?
Just ask me: [EMAIL PROTECTED]
On 15 Apr 2008, at 17:27, Torsten Foertsch wrote:
On Tue 15 Apr 2008, Mark Blackman wrote:
int main(int argc, char *argv){
fork();
printf(my pid is %d\n,getpid());
}
Please use the fork-syscall here not the C function.
i'm trying to test the C-library behaviour though?
in my case,
On Tue, Apr 15, 2008 at 8:28 AM, Mark Blackman [EMAIL PROTECTED] wrote:
modperl_perl_init_ids() which itself eventually does a
sv_setiv(GvSV(gv_fetchpv($, TRUE, SVt_PV)), ids-pid);
where ids-pid should contain the result of a recent getpid.
*However* I note that in the main perl code
On 15 Apr 2008, at 17:27, Torsten Foertsch wrote:
On Tue 15 Apr 2008, Mark Blackman wrote:
int main(int argc, char *argv){
fork();
printf(my pid is %d\n,getpid());
}
Please use the fork-syscall here not the C function.
Right, the C library will almost certainly use
the fork() call
On 15 Apr 2008, at 13:51, Mark Blackman wrote:
While I did find Torsten Förtsch's very useful Perl::AfterFork
module, surely the
mod_perl code must be doing something like this itself, no?
I'd be grateful to understand mod_perl's response to Perl's
pid caching is, given that forking *will*
21 matches
Mail list logo
