can you explain why this is important? I mean, why does mod_perl need to know the pid of the parent apache process? or, better, why is it important that mod_perl take the initiative and fix this. is a workaround patch in mod_perl core really required? what breaks if we don't fix it?
if any of your programs rely on geppid, they will now be either broken or don't do what you want. I've discovered it while porting Apache::VMonitor, which shows you all the httpd procs and their system's usage, calculating the memory usage and shared memory usage. getppid gives me 1, which completely blows out my algorithm for calculating shared memory usage since it needs to know the memory used by the parent httpd process.
ah, ok. thanks.
Besides it's a bug, no matter how you look at it, because a C call to getppid() from the same process will do the right thing.
ok.
It had to be fixed locally in mp2 since 5.8.1 has been released already, meaning that anybody who uses 5.8.1 is vulnerable to this problem. Hopefully 5.8.2 will get it fixed in perl.
well, I guess that was kinda my question. as an application itself, perl will always have bugs, so I guess I was asking if it was mod_perl's responsibility to "fix" these bugs internally.
but if you can't calculate memory usage accurately, that's probably a good enough reason so take care of it.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
