Just so you don't think I am not listening. I am reading each post with
great interest, waiting to see the outcome of this.
FWIW, I have been using Redhat's logrotate facility, and am starting to see
that it is flawed. I have always wondered how sites stayed up 24x7
Thanks for the excellent discussion
Dave
----- Original Message -----
From: "Ian Lance Taylor" <ian@airs.com>
To: "Lamar Owen" <lamar.owen@wgcr.org>
Cc: "Peter Eisentraut" <peter_e@gmx.net>; "Dave Cramer"
<Dave@micro-automation.net>; <pgsql-general@postgresql.org>
Sent: Wednesday, June 13, 2001 8:39 PM
Subject: Re: [GENERAL] Log files, how to rotate properly
> Lamar Owen <lamar.owen@wgcr.org> writes:
>
> > On Wednesday 13 June 2001 16:39, Peter Eisentraut wrote:
> > > Lamar Owen writes:
> > > > Use syslog. Syslog has many advantages:
> > > Disadvantage:
> >
> > > Some messages will get lost.
> >
> > I have yet to see a 'lost' syslog message here, in over three years.
> >
> > Which is worse, though:
> > 1.) An occasional lost log message;
> > 2.) Downtime due to pulling down the entire server to rotate a log.
> >
> > If syslog looses messages, let's try helping fix syslog rather than
> > recommending Yet Another Log Rotating Solution.
>
> The implementation of syslog--routing messages through a named pipe
> with a limited amount of buffer space--makes it inevitable that
> messages will be lost under heavy load. Sometimes heavy load is when
> you most need the messages.
>
> Also, under heavy load, syslog can fill up your disk.
>
> DJB's multilog program is a reliable alternative:
> http://cr.yp.to/daemontools.html
>
> Ian
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
>
