Here is a link to a thread where we came up with a perl solution for automagic log rotating based upon number of entries. This by-passes syslogd so it might or might not be useful to you.
Hello all.
Due to some reason I can not use HUP to rotate needed log files.
So I use the standard method:
cp $file $file.1
cat /dev/null > $file
But if Java application in this time writing the output to $file,
in the beginning of it appears many "^@^@^@^@^@^@".
How to avoid it? Or how... (6 Replies)
I have the below script to help with disk space cleanup that finds logs older than a specified number of days (say 10 days). I need it to grab "active" logs as well. Problem is an "active log" will not get archived unless I put in 0 days which I don't want to do, I need to leave the past 10 days,... (2 Replies)
I have application which to the heavy stdout and I have diverted the stdout to log file.
this log file is writing very heavily and we have a script which rotates the logs.
logic for rotation is smthing like
cp logfile logfile.1
cat /dev/null > logfile
this logic was working fine till we... (3 Replies)
hi folk,
need advise regarding the log rotation, i have the logadm set at
30 2 * * * /usr/sbin/logadm
so it supposed to rotate once per day, but now it rotated twice!
but someone my log will rotate at 2:30 AM, but then another 2 hours later, it creates a new and rotate a new log again,... (2 Replies)
Hi Guys,
Good morning, I just want to know and collect ideas on this one. Regarding rotation of logs as I've observed it's not consistently functioning. I have a server with 8 Partitions, each partition has a dedicated directory for the logs that is needed and I set it every 5mins (300secs) the... (1 Reply)
Hi All!
I seem to have a problem with log rotation, unless I am doing something wrong, I have type the following command for testing purposes to see if the -s option works but he did not:
logadm -w /var/adm/messages -C 8 -c -s 512k -t '/var/adm/messages.$n' -z 1
the file is now at this... (7 Replies)
I have an application that rotate its log once it reaches 100mb and it keeps a total of 24 logs. I am trying to write a script to run daily to tar up the previous day logs files and move them to a different directory. here is a long listing of the logs in the directory:
-rw-r--r-- 1 user1 ... (6 Replies)
In Mavericks, Apple has apparently moved control of log rotation to ASL. There's a 'ttl' value to determine how long log files will stick around for. I can compress them, change the way they're named, limit them by size, etc. But the one thing I cannot find is how to NOT keep one log file per... (0 Replies)
Hi All,
I have a situation here ...
HACMP is configured with application monitoring script, which is generating messages .... which is running every minute ...
And every minute when monitoring script run, one one log file is generating .... and this log file is rotating ...
which is rotating... (1 Reply)
Discussion started by: linux.amrit
1 Replies
LEARN ABOUT DEBIAN
plack::middleware::accesslog
Plack::Middleware::AccessLog(3pm) User Contributed Perl Documentation Plack::Middleware::AccessLog(3pm)NAME
Plack::Middleware::AccessLog - Logs requests like Apache's log format
SYNOPSIS
# in app.psgi
use Plack::Builder;
builder {
enable "Plack::Middleware::AccessLog", format => "combined";
$app;
};
DESCRIPTION
Plack::Middleware::AccessLog forwards the request to the given app and logs request and response details to the logger callback. The format
can be specified using Apache-like format strings (or "combined" or "common" for the default formats). If none is specified "combined" is
used.
This middleware uses calculable content-length by checking body type, and can not log the time taken to serve requests. It also logs the
request before the response is actually sent to the client. Use Plack::Middleware::AccessLog::Timed if you want to log details after the
response is transmitted (more like a real web server) to the client.
This middleware is enabled by default when you run plackup as a default "development" environment.
CONFIGURATION
format
enable "Plack::Middleware::AccessLog",
format => '%h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-agent}i"';
Takes a format string (or a preset template "combined" or "custom") to specify the log format. This middleware implements a subset of
Apache's LogFormat templates <http://httpd.apache.org/docs/2.0/mod/mod_log_config.html>:
%% a percent sign
%h REMOTE_ADDR from the PSGI environment, or -
%l remote logname not implemented (currently always -)
%u REMOTE_USER from the PSGI environment, or -
%t [local timestamp, in default format]
%r REQUEST_METHOD, REQUEST_URI and SERVER_PROTOCOL from the PSGI environment
%s the HTTP status code of the response
%b content length
%T custom field for handling times in subclasses
%D custom field for handling sub-second times in subclasses
%v SERVER_NAME from the PSGI environment, or -
%V HTTP_HOST or SERVER_NAME from the PSGI environment, or -
Some of these format fields are only supported by middleware that subclasses "AccessLog".
In addition, custom values can be referenced, using "%{name}", with one of the mandatory modifier flags "i", "o" or "t":
%{variable-name}i HTTP_VARIABLE_NAME value from the PSGI environment
%{header-name}o header-name header
%{time-format]t localtime in the specified strftime format
logger
my $logger = Log::Dispatch->new(...);
enable "Plack::Middleware::AccessLog",
logger => sub { $logger->log(level => 'debug', message => @_) };
Sets a callback to print log message to. It prints to "psgi.errors" output stream by default.
SEE ALSO
<http://httpd.apache.org/docs/2.2/mod/mod_log_config.html> Rack::CustomLogger
perl v5.14.2 2012-04-14 Plack::Middleware::AccessLog(3pm)