Properly document rotatelogs, and add mention of it to pg_ctl manual page.

This commit is contained in:
Bruce Momjian 2004-05-14 20:01:19 +00:00
parent 0cb27df5c6
commit 19a495caaa
2 changed files with 10 additions and 10 deletions

View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.33 2004/04/05 03:02:03 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.34 2004/05/14 20:01:19 momjian Exp $
-->
<chapter id="maintenance">
@ -461,7 +461,7 @@ VACUUM
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
rotation, the <application>rotatelogs</application> program can be
configured to work with log files from
<application>syslog</application>.
</para>
@ -484,12 +484,12 @@ VACUUM
pipe command:
<programlisting>
pg_ctl start | logrotate
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>logrotate</application>
Internet. For example, the <application>rotatelogs</application>
tool included in the <productname>Apache</productname> distribution
can be used with <productname>PostgreSQL</productname>.
</para>

View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.25 2003/11/29 19:51:39 pgsql Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.26 2004/05/14 20:01:19 momjian Exp $
PostgreSQL documentation
-->
@ -90,10 +90,10 @@ PostgreSQL documentation
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.
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>