tags #226138 - upstream
tags #226138 confirmed
notforwarded #226138
thanks
On Sun, Jan 04, 2004 at 10:21:05AM -0800, Tim Freeman wrote:
> Aide should return different error statuses depending on whether
> differences were found. Since aide always generates output now, and
> the exit status is meaningless, in the present situation I have to go
> parse the output to determine whether any checksums changed or not.
This has now changed upstream with 0.13:
DIAGNOSTICS
Normally, the exit status is 0 if no errors occurred. Except when the
--check command was requested, in which case the exit status is defined
as:
1 * (new files detected?) +
2 * (removed files detected?) +
4 * (changed files detected?)
Additionally, the following exit codes are defined for generic error
conditions:
14 Error writing error
15 Invalid argument error
16 Unimplemented function error
17 Invalid configureline error
18 IO error
I am thus removing the upstream and forwarded markers.
I am not closing the bug, since aide.wrapper does not yet hand the
exit code down to the calling code (making the exit code only useable
if you call aide directly with your own configuration), and the cron
job still parses the output instead of relying on the exit code.
Expect both of these things to change RSN, and expect this bug to be
(finally) closed soon.
Thanks for your patience.
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
