Am I right in assuming that you can use a command such as
#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t !tai64nlocal
/var/log/qmail/smtpd
for logging qmail-smtpd and this will process the log through tai64nlocal
*after* completing the log?
I got this from skimming the page http://cr.yp.to/daemontools/multilog.html
and specifically the last section !processor on that page.
-----Original Message-----
From: A Hoffman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 02, 2000 3:30 PM
To: [EMAIL PROTECTED]
Subject: Re: multilog datestamping
Thanks Chris. Now that begs the question of why I should use multilog
instead of syslog which does datestamp if you tell it to. It doesn't seem
beneficial to add a superflous step. I apologize if this point seems
irrelevant.
However if there is a better method, I would appreciate pointers to the
documentation.
- Aodhan
On Wed, 2 Feb 2000, Chris Johnson wrote:
> On Wed, Feb 02, 2000 at 11:20:30AM -0800, A Hoffman wrote:
> > On that note, what is an example of a startup script that includes
useful
> > datestamping for multilog? I used the examples set forward in section
2.8.2.
> > 'System start-up files' in LWQ, and it is not working as I had hoped.
Thanks!
>
> Don't try to do it from your startup file. When you want to look at the
logs
> and see time stamps that mean something to you, pipe the log through
tailocal
> or tai64nlocal (for cyclog and multilog files respectively).
>
> Chris
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-:
Aodhan of Mountainview
Internet Guy
Ad Astra Per Aspera
"A Rough Road Leads To The Stars"
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-:
