Hello,
Unfortunately Jorge's patch is incomplete. The reason for the looping on
pid is that, if nproc > 1, the pidfile will contain more than one PID
and using --pidfile will only kill the first one.
The proposed patch here will fix both situation, i.e. the fact that
--pid is silently ignored and
The "new bug" for trusty concerning if nproc > 1 is probably this one:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737 ?
--
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
Good catch Claudio. The bug is present in Trusty and Trusty-backports.
Prior to LP: #1477198, the stop script did not stop at all because it
relied on the --pid option that is introduced in dpkg version 1.17.6 as
outlined in the man page of start-stop-daemon :
[--pid] pid
Ch
Peter, you will not be able to reproduce on Debian unless you test
versions prior to Stable.
The reason why the stop script does not stop at all processes is because
it relied on the --pidfile option and this one only kills the first PID.
When nproc > 1, the PIDFILE contains all PIDs. This is why
FYI, I will rebase the debdiff on the new version currently in backport
& repost.
--
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/1494141
Title:
HAProxy 1.5 init script do
Hi Louis !
Yes, I have the same understanding of the problem ! So if the fix is available,
and you do port it, I guess you can close the ticket :)
Thanks a lot for you work and effort !
Br,
Peter.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, w
6 matches
Mail list logo