Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

qmail2dlf(1) [debian man page]

QMAIL2DLF.IN(1) 					  LogReport's Lire Documentation					   QMAIL2DLF.IN(1)

NAME
qmail2dlf - convert sanitized qmail-send logs to dlf SYNOPSIS
qmail2ldf DESCRIPTION
qmail2dlf reads qmail-send logs from stdin, writes dlf to stdout, and, in case of errors, complains on stderr. TIMESTAMPS
We expect timestamps which look like e.g. `977359048.466280500' in our log: number of seconds since the epoch, in any precision. The log should feature lines which look something like: 982584201.511524 info msg 6426: bytes 3537 from <qmail-return-63074-joostvb=mdcc.cx@list.cr.yp.to> qp 21089 uid 70 splogger, as distributed with qmail, writes `a numerical timestamp', ie something like 972802273.627578, indicating seconds and nanoseconds since the beginning of 1970. multilog, as distributed with daemontools, http://cr.yp.to/daemontools.html, if invoked with action t, writes a `@' and a tai64n format timestamp. These timestamps look like e.g. 4000000039ef8532346bb35c. Note that 0x400000000000000000000000 is 2^62. One can get the current time in tai64 format by doing: echo 40000000`(echo obase = 16; date +%s) | bc`00000000 (assuming GNU date is installed) To convert tai64n to numerical timestamps, one can use Russ Allbery's tai64nfraq. It's in the public domain, available from http://www.qmail.org/tai64nfrac. EXAMPLE
To process a log as produced by splogger: $ lr_desyslog qmail < mail.log | qmail2dlf To process a log as produced by multilog: $ tai64nfrac < current | qmail2dlf qmail2dlf(1) will be rarely used on its own, but is more likely called by lr_log2report: $ tai64nfrac < /service/qmail-send/log/main/current | lr_log2report qmail BUGS
We don't deal with bounces: email qmail none qmail2dlf info skipping line '986244190.800217 bounce msg 6306 qp 28445': first field should be one of 'new', 'info', 'starting', 'delivery', 'end' or 'status:', not 'bounce' qmail2dlf doesn't use any information from the qmail-smtpd(1) logs. (These look like 2002-06-16 09:34:57.798038500 tcpserver: pid 19385 from 100.61.24.7 2002-06-16 09:34:58.114198500 tcpserver: ok 19385 foo.example.com:100.163.25.11:25 logreport.iae.nl:212.61.24.7:postfix:1189 .) VERSION
$Id: qmail2dlf.in,v 1.24 2006/07/23 13:16:34 vanbaal Exp $ COPYRIGHT
Copyright (C) 2000, 2001 Stichting LogReport Foundation LogReport@LogReport.org This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (see COPYING); if not, check with http://www.gnu.org/copyleft/gpl.html. AUTHOR
Joost van Baal <joostvb@logreport.org> Lire 2.1.1 2006-07-23 QMAIL2DLF.IN(1)

Check Out this Related Man Page

LR_RUN.IN(1)						  LogReport's Lire Documentation					      LR_RUN.IN(1)

NAME
lr_run - run a Lire program and deal with the logging output SYNOPSIS
lr_run program arguments DESCRIPTION
lr_run runs program, and redirects program's stderr output to logger(1). It parses programs logging output, and sets logger(1)'s flags accordingly. lr_run gets configuration from sysconfdir/lire/defaults. In case 'lr_logging_method' is set to 'stderr', logger(1) is not involved: logging output gets redirected to stderr. In case 'lr_debug' is set to the empty string, messages with loglevel debug and info get suppressed. The configuration variable 'lr_logging_facility' is used to find logger(1)'s facility. NOTES
program's output on stderr should be in format superservice service id programname level message. level should be one of: emerg (system is unusable), alert (action must be taken immediately), crit (critical conditions), err (error conditions), warning (warning conditions), notice (normal, but significant, condition), info (informational message), debug (debug-level message). See syslog(3). id can be used to tag each Lire job, so that these can get tracked. programname should be the name of the program which generated the log line. EXAMPLES
To process a Postfix log and display the report as text, use $ lr_run lr_log2report postfix < /var/log/mail.log To process a Postfix log and create the report in HTML (packed up in a tar archive), use: $ lr_run lr_log2report -o html postfix < /var/log/mail.log > postfix.tar SEE ALSO
Documentation in the Lire User Manual VERSION
$Id: lr_run.in,v 1.23 2006/07/23 13:16:33 vanbaal Exp $ COPYRIGHT
Copyright (C) 2000-2003 Stichting LogReport Foundation LogReport@LogReport.org This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (see COPYING); if not, check with http://www.gnu.org/copyleft/gpl.html. THANKS
Rudi Sluijtman, for sharing some thoughts on shell scripting. AUTHOR
Joost van Baal <joostvb@logreport.org> Lire 2.1.1 2006-07-23 LR_RUN.IN(1)
Man Page