Mailing-List: contact modperl-help@apache.org; run by ezmlm
Precedence: bulk
Message-Id: <200202120231.g1C2VQe31142@tzimisce.cygnus.com>
To: modperl@apache.org
Reply-to: rjray@redhat.com (Randy J. Ray)
Subject: About PerlLogHandler phase
Date: Mon, 11 Feb 2002 18:31:25 -0800
From: "Randy J. Ray" <rjray@redhat.com>

Having gone over the Eagle book and the sample chapter of the cookbook (great
luck that, having one of the sample chapters coincidentally be the one that
covers the logging phase, since I haven't gotten my copy yet), I am still
unclear on a few things regarding the logging phase:

* If I install a handler for PerlLogHandler, does the normal logging still
  take place? Is it a function of whether my handler returns OK, DECLINED,
  etc.?

* Are there ways to register other log types, in addition to the access,
  error, etc.? Such that people could specify those (and a format) the
  same way they specify the others? More to the point, so that there
  might be a ready file-descriptor I could print to, rather than having to
  deal with the open/lock/write/unlock/close cycle.

To explain, I am looking at ways to expand the logging capability in my
Apache::RPC::Server class. I'd like at the very least to be able to alter the
URI part such that it reflects the procedure name that was called (this I
understand how to do). Ideally, I'd like to either write completely different
lines out to the access log, or (preferable) write to a separate log entirely,
so that tracking usage statistics is made that much easier. If I go the
separate log route, I don't want the server to be weighted down by the
repetitive open/close cycle on the files.

Randy
--
-------------------------------------------------------------------------------
Randy J. Ray     | Men occasionally stumble over the truth, but most of them
rjray@redhat.com | pick themselves up and hurry off as if nothing had happened.
+1 408 543-9482  |   -- Sir Winston Churchill