On Mon, 2012-06-25 at 12:50 -0300, Cleber Rosa wrote: > On 06/25/2012 12:46 PM, Spear, Raymond (Mission Critical Linux) wrote: > > humm... playing with this futher. > > > > What should this do: > > > > autotest-rpc-client host list badhost goodhost > > > > It will fail to find "badhost" but it will find "goodhost". > > > > One can make the argument that the command failed to find ALL systems and > > should exit non-zero. But on the other hand it did find some and so wasn't > > a "total failure". Is there the need for a "tri-state" exit?? > > 0 - all systems listed found > > 1 - no systems listed found > > 2 - some systems listed found > > I wouldn't say we *need* this tri-state exit code, but we could have it > if it's useful. Many apps (rsync comes to my mind) have very rich set of > return codes that communicate partial success and other special conditions.
In that case, it's very necessary to document the exit code [1], so callers know how to handle each condition. [1] At least in the docstring, but updating the wiki CLI docs is necessary as well. _______________________________________________ Autotest mailing list Autotest@test.kernel.org http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
