Log::Agent::Channel::File - file logging channel for Log::Agent |
Log::Agent::Channel::File - file logging channel for Log::Agent
require Log::Agent::Channel::File;
my $driver = Log::Agent::Channel::File->make( -prefix => "prefix", -stampfmt => "own", -showpid => 1, -magic_open => 0, -filename => "/tmp/output.err", -fileperm => 0640, -share => 1, );
The file channel performs logging to a file, along with the necessary prefixing and stamping of the messages.
Internally, the Log::Agent::Driver::File
driver creates such objects
for each logging channel defined at driver creation time.
The creation routine make()
takes the following arguments:
-filename
=> file-magic_open
flag.
-fileperm
=> permopen()
and sysopen(), the value
is limited to less than or equal to 0666. See perlfunc(3)/umask for more
details.
-magic_open
=> flagsysopen()
is used, in append mode.
Default is false.
-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-rotate
=> objectLog::Agent::Rotate
module to use this switch.
object is the Log::Agent::Rotate
instance describing the rotating
policy for the channel. Only files which are not opened via a
so-called magic open can be rotated.
-share
=> flagHowever, you will get this message in the file
Rotation for 'filename' may be wrong (shared with distinct policies)
when a rotation policy different from the one used during the initial opening is given. Which policy will be used is unspecified, on purpose.
-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.
Originally written by Raphael Manfredi <Raphael_Manfredi@pobox.com>, currently maintained by Mark Rogaski <mrogaski@cpan.org>.
Copyright (C) 1999 Raphael Manfredi. Copyright (C) 2002 Mark Rogaski, mrogaski@cpan.org; all rights reserved.
See the Log::Agent(3) manpage or the README file included with the distribution for license information.
Log::Agent::Logger(3), Log::Agent::Channel(3).
Log::Agent::Channel::File - file logging channel for Log::Agent |