Add mention of logrotate for syslog, from Robert Treat

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 1affca872a76bcfad28840d7c8cdaf980491c45f..e9e17ea2f40011bbcb6c82604e6e979297b84925 100644 (file)
--- 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 d1b398425dc76e9913c659ae99a13031201cebc6..4854d0fbaebb1fde9b7c35bbe2847ba2121a0291 100644 (file)
--- 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.