Commit fc796286 authored by Bruce Momjian's avatar Bruce Momjian

Clarify tar documentation about return error codes.

Backpatch to 8.2.X.
parent ae36e0d5
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.100 2007/09/14 04:15:50 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.101 2007/09/14 13:26:22 momjian Exp $ -->
<chapter id="backup"> <chapter id="backup">
<title>Backup and Restore</title> <title>Backup and Restore</title>
...@@ -735,11 +735,11 @@ SELECT pg_stop_backup(); ...@@ -735,11 +735,11 @@ SELECT pg_stop_backup();
of <application>rsync</> return a separate exit code for of <application>rsync</> return a separate exit code for
<quote>vanished source files</>, and you can write a driver script to <quote>vanished source files</>, and you can write a driver script to
accept this exit code as a non-error case. Also, some versions of accept this exit code as a non-error case. Also, some versions of
GNU <application>tar</> consider it an error if a file was truncated GNU <application>tar</> return an error code indistinguishable from
while <application>tar</> is copying it. Fortunately, GNU a fatal error if a file was truncated while <application>tar</> was
<application>tar</> versions 1.16 and later exits with <literal>1</> copying it. Fortunately, GNU <application>tar</> versions 1.16 and
if a file was changed during the backup, and <literal>2</> for other later exits with <literal>1</> if a file was changed during the backup,
errors. and <literal>2</> for other errors.
</para> </para>
<para> <para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment