For the next release of my RPC::XML package, I plan to roll out a status
tracker akin to Apache::Status in mod_perl, only to monitor/examine the RPC
servers being managed by the mod_perl-ennabled Apache server. I would like to
have the main page of this Apache::RPC::Status system offer a link to
Randy J. Ray wrote:
For the next release of my RPC::XML package, I plan to roll out a status
tracker akin to Apache::Status in mod_perl, only to monitor/examine the RPC
servers being managed by the mod_perl-ennabled Apache server. I would like to
have the main page of this
Since this section ss probably going away, here it is:
The syslog solution can be implemented using the following
configuration:
LogFormat %h %l %u %t \%r\ %s %b common
CustomLog | /usr/local/apache/bin/syslogger.pl hostnameX common
where a simple Isyslogger.pl can look like this:
Texas AM University just opened a position for a software applications
developer. You would be working (most likely) with me developing web
applications and other code to enable system functions. You would need to
relocate to the Bryan/College Station area.
Notice of vacancy:
Please see if you notice anything glaringly wrong in what I'm doing.
Basically my problem is that my filter isn't passing data along, eg what I
print in filter1 isn't getting output, even though filter2 get's the
filehandle and loops over it. My setup is pretty akin to what the docs offer
in
I tried out your config and handlers pretty much verbatim and got them
to work just fine. the only real change was that I needed to comment
out
return $status unless $status == OK;
from filter one, since $fh is $r-filename for the first filter, which
brings up 404 when the file is
ok, that make sense, so I modified my filter1 to just register the filter,
print out some text, and return ok, that's it. and it still doesn't print
anything if filter2 comes after it? Does that sound wrong to anybody but me?
On Friday 07 December 2001 12:47 pm, you wrote:
I tried out your
Jason Hall wrote:
ok, that make sense, so I modified my filter1 to just register the filter,
print out some text, and return ok, that's it. and it still doesn't print
anything if filter2 comes after it? Does that sound wrong to anybody but me?
try this:
package One;
use
AHAH!!! I found it.. thanks, your example showed the difference.
What it was is that I was sending my header before my final filter, which as
I now am guessing, maps STDOUT, which this needs. I'm recommending to the
author to put a note in about where the headers should be printed.
Thanks
Jason Hall wrote:
AHAH!!! I found it.. thanks, your example showed the difference.
What it was is that I was sending my header before my final filter, which as
I now am guessing, maps STDOUT, which this needs.
well, you should be able to print your headers from any filter in the
chain
stas01/12/07 10:12:17
Modified:ModPerl-Registry TODO
Log:
- todo: need to properly handle HEAD requests
Revision ChangesPath
1.7 +2 -0 modperl-2.0/ModPerl-Registry/TODO
Index: TODO
===
11 matches
Mail list logo
