On 9/6/2012 5:23 AM, Dominique Leuenberger a.k.a DimStar wrote:
Quoting "Brian K. White" <brian@aljex.com>:
Another example I saw a while back was rsync. rsync hasd had a certain set of exit values with various meanings, all nicely documented in their man pages and also predating systemd by over 10 years? Yet systemd called rsync's behavior a bug because there were some exit values other than 0 that didn't necessarily indicate an error.
Yet, this example is solved in systemd already:
(extract from http://www.freedesktop.org/software/systemd/man/systemd.service.html) SuccessExitStatus=
Takes a list of exit status definitions that when returned by the main service process will be considered successful termination, in addition to the normal successful exit code 0 and the signals SIGHUP, SIGINT, SIGTERM and SIGPIPE. Exit status definitions can either be numeric exit codes or termination signal names, and are are separated by spaces. Example: "SuccessExitStatus=1 2 8 SIGKILL", ensures that exit codes 1, 2, 8 and the termination signal SIGKILL are considered clean service terminations.
Ok that's a start! -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org