Index: maintenance.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/maintenance.sgml,v
retrieving revision 1.33
diff -c -c -r1.33 maintenance.sgml
*** maintenance.sgml	5 Apr 2004 03:02:03 -0000	1.33
--- maintenance.sgml	14 May 2004 19:57:46 -0000
***************
*** 461,467 ****
     you can send a <literal>SIGHUP</literal> signal to the
     <application>syslog</> daemon whenever you want to force it to
     start writing a new log file.  If you want to automate log
!    rotation, the <application>logrotate</application> program can be
     configured to work with log files from
     <application>syslog</application>.
    </para>
--- 461,467 ----
     you can send a <literal>SIGHUP</literal> signal to the
     <application>syslog</> daemon whenever you want to force it to
     start writing a new log file.  If you want to automate log
!    rotation, the <application>rotatelogs</application> program can be
     configured to work with log files from
     <application>syslog</application>.
    </para>
***************
*** 484,495 ****
     pipe command:
  
  <programlisting>
! pg_ctl start | logrotate
  </programlisting>
  
     The <productname>PostgreSQL</> distribution doesn't include a
     suitable log rotation program, but there are many available on the
!    Internet. For example, the <application>logrotate</application>
     tool included in the <productname>Apache</productname> distribution
     can be used with <productname>PostgreSQL</productname>.
    </para>
--- 484,495 ----
     pipe command:
  
  <programlisting>
! pg_ctl start | rotatelogs /var/log/pgsql_log 86400
  </programlisting>
  
     The <productname>PostgreSQL</> distribution doesn't include a
     suitable log rotation program, but there are many available on the
!    Internet. For example, the <application>rotatelogs</application>
     tool included in the <productname>Apache</productname> distribution
     can be used with <productname>PostgreSQL</productname>.
    </para>
Index: ref/pg_ctl-ref.sgml
===================================================================
RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_ctl-ref.sgml,v
retrieving revision 1.25
diff -c -c -r1.25 pg_ctl-ref.sgml
*** ref/pg_ctl-ref.sgml	29 Nov 2003 19:51:39 -0000	1.25
--- ref/pg_ctl-ref.sgml	14 May 2004 19:57:46 -0000
***************
*** 87,99 ****
     server is started in the background, and standard input is attached to
     <filename>/dev/null</filename>.  The standard output and standard
     error are either appended to a log file (if the <option>-l</option>
!    option is used), or redirected to  <application>pg_ctl</application>'s 
     standard output (not standard error).  If no log file is chosen, the 
     standard output of <application>pg_ctl</application> should be redirected 
!    to a file or piped to another process, for example a log rotating program,
!    otherwise <command>postmaster</command> will write its output to the controlling
!    terminal (from the background) and will not leave the shell's
!    process group.
    </para>
  
    <para>
--- 87,99 ----
     server is started in the background, and standard input is attached to
     <filename>/dev/null</filename>.  The standard output and standard
     error are either appended to a log file (if the <option>-l</option>
!    option is used), or redirected to <application>pg_ctl</application>'s 
     standard output (not standard error).  If no log file is chosen, the 
     standard output of <application>pg_ctl</application> should be redirected 
!    to a file or piped to another process such as a log rotating program
!    like <application>rotatelogs</>; otherwise the <command>postmaster</command> 
!    will write its output to the controlling terminal (from the background) 
!    and will not leave the shell's process group.
    </para>
  
    <para>