From owner-freebsd-hackers Fri Jul 10 02:49:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15595 for freebsd-hackers-outgoing; Fri, 10 Jul 1998 02:49:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15589; Fri, 10 Jul 1998 02:49:26 -0700 (PDT) (envelope-from jkoshy@FreeBSD.org) From: Joseph Koshy Received: (from jkoshy@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id CAA01481; Fri, 10 Jul 1998 02:49:26 -0700 (PDT) Date: Fri, 10 Jul 1998 02:49:26 -0700 (PDT) Message-Id: <199807100949.CAA01481@freefall.freebsd.org> To: freebsd-hackers@FreeBSD.ORG Subject: Do you rely on "dump"s (currently incorrect) exit codes? Cc: jkoshy@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm planning a straight-forward change to "dump" to make its exit codes confirm to the man page. Currently "dump" returns "3" (i.e. non-recoverable error) in a number of places where it should return "1" (startup error). No big deal. My concern however, is that people may be using the `wrong' return values in their backup scripts. If you feel you are going to be badly affected by such a change and if you feel this change shouldn't take place, please speak up now! (PR: 5346) Koshy (who would rather not pull the rug from under some hapless sysadmin relying on the incorrect exit codes :-)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message