haproxy init script gives incorrect exit status

[Aaron Kaplan]

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.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "haproxy-init-script-exit-status.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Launchpad Janitor (janitor)]

This bug was fixed in the package haproxy - 1.4.24-1

---------------
haproxy (1.4.24-1) unstable; urgency=high

  [ Vincent Bernat ]
  * New upstream version.
     + CVE-2013-2175: fix a possible crash when using negative header
       occurrences.

  [ Prach Pongpanich ]
  * Drop bashism patch. It seems useless to maintain a patch to convert
    example scripts from /bin/bash to /bin/sh.
  * Fix reload/restart action of init script (LP: #1187469).

 -- Vincent Bernat <email address hidden> Mon, 17 Jun 2013 21:56:26 +0200