exit code is always 0
Bug #1040995 reported by
John M
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Back In Time |
Fix Released
|
Medium
|
Unassigned |
Bug Description
It appears that backintime always returns an exit code of 0. This makes proper scripting difficult. I run backintime from a cron job and there's no way to check if it failed. Which means I have to manually check everyday if the backup ran.
It should return a non-zero exit code in case of some failure, as is standard for any console program. I understand that there is some kind of of callback mechanism that one can use, but simply fixing the application return code to work properly would be nicer.
Related branches
Changed in backintime: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in backintime: | |
milestone: | none → 1.1.0 |
Changed in backintime: | |
status: | Confirmed → Fix Committed |
Changed in backintime: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
+1
Really make scripting impossible. Should comply to Linux standard exit codes.
Looks like a quick fix