Actions
User story #3805
closedrudder-agent init should return non-zero (0) on status operation if is not running
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
When we run :
/etc/init.d/rudder-agent status
We always get a $? (return code) of 0, even if nothing is working. This should be non-zero if status is not OK.
Updated by Jonathan CLARKE over 11 years ago
- Tracker changed from Bug to User story
- Subject changed from rudder-agent init script doesn't always returns 0 on status operation to rudder-agent init should return non-zero (0) on status operation if is not running
Updated by Jonathan CLARKE over 11 years ago
- Status changed from In progress to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:ea0ba985ecda6573695b90706ff9fdf0e24742c6.
Updated by Nicolas PERRON over 11 years ago
Applied in changeset commit:c8cdce113003e2e941a8bbce4894f2f2308de282.
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.7.1 to 2.7.0
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Updated by Nicolas PERRON over 11 years ago
This bug has been fixed in Rudder 2.7.0, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000043.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog27
- Download information: http://www.rudder-project.org/foswiki/Download/
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions