Public bug reported:
In /etc/init.d/haproxy, the reload and restart commands always exit with
status 0 (success), even when the haproxy command failed. reload and
restart should be rewritten to follow the pattern of start and stop,
which give informative exit codes.
I'm using ubuntu 12.04, but the problem still appears to exist in 13.04.
** Affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "haproxy-init-script-exit-status.patch"
https://bugs.launchpad.net/bugs/1187469/+attachment/3694553/+files/haproxy-init-script-exit-status.patch
** Description changed:
In /etc/init.d/haproxy, the reload and restart commands always exit with
status 0 (success), even when the haproxy command failed. reload and
- restart should be rewritten to follow the pattern of start and stop.
+ restart should be rewritten to follow the pattern of start and stop,
+ which give informative exit codes.
I'm using ubuntu 12.04, but the problem still appears to exist in 13.04.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1187469
Title:
haproxy init script gives incorrect exit status
Status in “haproxy” package in Ubuntu:
New
Bug description:
In /etc/init.d/haproxy, the reload and restart commands always exit
with status 0 (success), even when the haproxy command failed. reload
and restart should be rewritten to follow the pattern of start and
stop, which give informative exit codes.
I'm using ubuntu 12.04, but the problem still appears to exist in
13.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1187469/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
