On Thu, Sep 06, 2012 at 05:01:52AM -0400, Brian K. White wrote: [snip] Hallo Brian,
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.
Rather than add a feature to systemd such that a unit author could define the behavior of the daemon, no, they tell the daemon that it's behavior is a bug.
you have to update your set of systemd's faults, because that has been discussed http://lists.freedesktop.org/archives/systemd-devel/2012-August/006188.html """ Hmm, I was kinda waiting for use cases like this. i.e. before we add an option to reconfigure what clean exits are I wanted an explicit request for it, so that we don't end up adding something that is actually unncessary. Added this to the TODO list now. """ ... and in a meanwhile .. http://lists.freedesktop.org/archives/systemd-commits/2012-August/002397.htm... +* add option to reconfigure success exit codes/signals for services + ... fixed ... http://lists.freedesktop.org/archives/systemd-commits/2012-August/002414.htm... ... and released ... http://cgit.freedesktop.org/systemd/systemd/tree/NEWS CHANGES WITH 189: ... * There are two new service settings RestartPreventExitStatus= and SuccessExitStatus= which allow configuration of exit status (exit code or signal) which will be excepted from the restart logic, resp. consider successful. BTW: I am curious why too many people claims Lennart does not want to do something without even proposing it on systemd-devel ... Regards Michal Vyskocil