> > print STDERR
>
> I don't use "print STDERR" much. So, I am not sure if you have to set
> $|=1 for
> the handle. What happens if you replace "print STDERR" by "warn"? The
> postconfig phase comes after openlogs. So, STDERR should point to the
> main
> server errorlog.
For now, to avoid any such issues, I am writing to files under /tmp,
a different once for each phase. For OpenLogs, PostConfig and
ChildInit, I am fine.
For PostReadRequest, I get nothing.
They are configured as follows:
PerlPostReadRequestHandler Rosalind::Phase::PostReadRequest
PerlOpenLogsHandler Rosalind::Phase::OpenLogs
PerlPostConfigHandler Rosalind::Phase::PostConfig
PerlChildInitHandler Rosalind::Phase::ChildInit
And the PostReadRequest handler, with perms 644, is as follows:
package Rosalind::Phase::PostReadRequest;
use Apache2::Const -compile => 'OK';
sub handler {
open my $fh,">>/tmp/PostReadRequest" or die "Nope: $!";
print $fh "pid: $$\n";
close $fh;
return Apache2::Const::OK;
}
1;
Josh Narins
Director of Application Development
SeniorBridge
845 Third Ave
7th Floor
New York, NY 10022
Tel: (212) 994-6194
Mobile: (917) 488-6248
Fax: (212) 994-4260
jnar...@seniorbridge.com
SeniorBridge
Managing Complex Chronic Care
http://www.seniorbridge.com
SeniorBridge Statement of Confidentiality: The contents of this email message
are intended for the exclusive use of the addressee(s) and may contain
confidential or privileged information. Any dissemination, distribution or
copying of this email by an unintended or mistaken recipient is strictly
prohibited. In said event, kindly reply to the sender and destroy all entries
of this message and any attachments from your system. Thank you.
