I have no idea. You were the one who suggested this solution back in July and you said that it just worked, when I said that I was skeptical about it ;)If I remember correctly, you mentioned this to me back at YAPC::Paris in July. But back then you said you are going to gracefully restart the child processes, after updating the parent's data so that the newly spawned processes will see the updated info. It won't work in any other way.Having to gracefully restart is what I'm trying to prevent, really. My experience so far with grceful restarts hasn't been very favourable. Was I wrong?
I think I said it _should_ work... ;-)
They all run in the child. The only hooks run by the parent process that spawns the child processes is PostConfig and OpenLogs, which happen at the server startup.If you are talking about serving HTTP, you probably want PerlInitHandler. Similar to Apache::Reload.But PerlInitHandler runs in the child, does it not?
Ok, so much for that idea then... if there is no handler running in the parent for each request, then my idea won't fly... unless I do all of this in a signal handler in the parent...would that fly? Something like this in PerlRequire:
my $updating;
$SIG{123} = sub {
return if $updating++; # make sure only one at a time
#update data structures;
$updating = 0;
};Liz
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
