Re: expanding on syslog help

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: expanding on syslog help
Date: 2003-10-09 19:04:34
Message-ID: 200310091904.h99J4Y417668@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Treat wrote:
> On Tue, 2003-09-30 at 01:44, Christopher Kings-Lynne wrote:
> > * Mention that you might want to turn log_pid and log_timestamp off
> > since syslog logs them anyway
> >
>
> i think that debug_pretty_print is somewhat pointless too, as syslog
> tends to wrap lines automagically... could be others.
>
> > * Mention something about system log rotator? Or is that too
> > platform-specific?
> >
>
> "The simplest production-grade approach to managing log output is to
> send it all to syslog and let syslog deal with file rotation. To do
> this, set the configurations parameter syslog to 2 (to log to syslog
> only) in postgresql.conf. Then you can send a SIGHUP signal to the
> syslog daemon whenever you want to force it to start writing a new log
> file. "
>
> Perhaps add:
> "If you want to automate the log rotation, the logrotate program can be
> configured to work with log files from syslog."
>
> at least, on most linux distros (and I'm just guessing others) this is
> how they come configured.

Added. Thanks.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-10-09 19:05:28 Re: [HACKERS] [COMMITTERS] pgsql-server/src/template bsdi
Previous Message Jan Wieck 2003-10-09 18:44:07 Re: [HACKERS] [COMMITTERS] pgsql-server/src/template bsdi