Date: Fri, 19 Dec 1997 13:32:06 -0800 (PST) From: paco@cs.virginia.edu To: freebsd-gnats-submit@FreeBSD.ORG Subject: bin/5346: Discrepancy between dump(8) man page and behavior Message-ID: <199712192132.NAA20202@hub.freebsd.org> Resent-Message-ID: <199712192140.NAA20977@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 5346
>Category: bin
>Synopsis: Discrepancy between dump(8) man page and behavior
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Dec 19 13:40:00 PST 1997
>Last-Modified:
>Originator: Paco Hope
>Organization:
University of Virginia
>Release: 2.1.5-RELEASE
>Environment:
FreeBSD xxx.xxx.edu 2.1.5-RELEASE FreeBSD 2.1.5-RELEASE #1: Thu Aug 21 15:42:54 EDT 1997 root@xxx.xxx.edu:/usr/src/sys/compile/AIDA i386
>Description:
The man page to dump says this:
Dump exits with zero status on success. Startup errors are indicated
with an exit code of 1; abnormal termination is indicated with an exit
code of 3.
The source code to dump says this:
#define X_FINOK 0 /* normal exit */
#define X_REWRITE 2 /* restart writing from the check point */
#define X_ABORT 3 /* abort dump; don't attempt checkpointing */
In practice, dump exits with error codes 0,1,2, or 3. It would
be nice if these things were properly documented so that people
could rely on the error code just a little. I discovered this
bug on linux, too, so it's probably been in the source for a
while.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712192132.NAA20202>