Log::Agent::Channel::Handle - I/O handle logging channel for Log::Agent |
Log::Agent::Channel::Handle - I/O handle logging channel for Log::Agent
require Log::Agent::Channel::Handle;
my $driver = Log::Agent::Channel::Handle->make( -prefix => "prefix", -stampfmt => "own", -showpid => 1, -handle => \*FILE, );
The handle channel performs logging to an already opened I/O handle, along with the necessary prefixing and stamping of the messages.
The creation routine make()
takes the following arguments:
-handle
=> handle\*FILE
, or as an IO::Handle
object.
NOTE: Auto-flushing is not enabled on the handle. Even when the channel is closed, the handle is left as-is: we simply stop sending log messages to it.
-no_newline
=> flagInternally, Log::Agent relies on the channel to delimit logged lines
appropriately, so this flag is not used. However, it might be useful
for Log::Agent::Logger
users.
Default is false, meaning newline markers are systematically appended.
-no_prefixing
=> flag-prefix
, -showpid
,
-no_ucfirst
, -stampfmt
.
Default is false.
-no_ucfirst
=> flagDefault is false, meaning uppercasing is performed.
-prefix
=> prefix-showpid
=> flagDefault is false.
-stampfmt
=> (name | CODE)You may also specify a CODE ref: that routine will be called every time we need to compute a time stamp. It should not expect any parameter, and should return a string.
Beware of chdir(). If your program uses chdir(), you should always specify logfiles by using absolute paths, otherwise you run the risk of having your relative paths become invalid: there is no anchoring done at the time you specify them. This is especially true when configured for rotation, since the logfiles are recreated as needed and you might end up with many logfiles scattered throughout all the directories you chdir()ed to.
Raphael Manfredi <Raphael_Manfredi@pobox.com>
Log::Agent::Logger(3), Log::Agent::Channel(3).
Log::Agent::Channel::Handle - I/O handle logging channel for Log::Agent |