From c7c7861d5e8daede5ead93e1c80cf08507787b21 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 9 Oct 2003 19:05:09 +0000 Subject: [PATCH] Add mention of logrotate for syslog, from Robert Treat --- doc/src/sgml/maintenance.sgml | 17 +++++++++-------- doc/src/sgml/runtime.sgml | 6 +++--- 2 files changed, 12 insertions(+), 11 deletions(-) diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 1affca872a..e9e17ea2f4 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,5 +1,5 @@ @@ -422,13 +422,14 @@ VACUUM 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. + 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. If you want to automate log rotation, + the logrotate program can be configured to work with log files from syslog. + diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index d1b398425d..4854d0fbae 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1863,8 +1863,8 @@ SET ENABLE_SEQSCAN TO OFF; Prefixes each message in the server log file with the process ID of the server process. This is useful to sort out which messages pertain to which connection. The default is off. This parameter - does not affect messages logged via syslog, which always contain - the process ID. + does not affect messages logged via syslog, which + always contain the process ID. -- 2.40.0