mirror of
https://github.com/borgbackup/borg.git
synced 2024-12-24 08:45:13 +00:00
document return codes
This commit is contained in:
parent
4b81f380f8
commit
05b21e3c0d
1 changed files with 21 additions and 0 deletions
|
@ -17,6 +17,27 @@ messages as it is processing.
|
||||||
|
|
||||||
.. include:: usage/init.rst.inc
|
.. include:: usage/init.rst.inc
|
||||||
|
|
||||||
|
Return codes
|
||||||
|
------------
|
||||||
|
|
||||||
|
|project_name| can exit with the following return codes (rc):
|
||||||
|
|
||||||
|
::
|
||||||
|
|
||||||
|
0 no error, normal termination
|
||||||
|
1 some error occurred (this can be a complete or a partial failure)
|
||||||
|
128+N killed by signal N (e.g. 137 == kill -9)
|
||||||
|
|
||||||
|
|
||||||
|
Note: we are aware that more distinct return codes might be useful, but it is
|
||||||
|
not clear yet which return codes should be used for which precise conditions.
|
||||||
|
|
||||||
|
See issue #61 for a discussion about that. Depending on the outcome of the
|
||||||
|
discussion there, return codes may change in future (the only thing rather sure
|
||||||
|
is that 0 will always mean some sort of success and "not 0" will always mean
|
||||||
|
some sort of warning / error / failure - but the definition of success might
|
||||||
|
change).
|
||||||
|
|
||||||
Examples
|
Examples
|
||||||
~~~~~~~~
|
~~~~~~~~
|
||||||
::
|
::
|
||||||
|
|
Loading…
Reference in a new issue