[Bug 221402] [PATCH] net/haproxy: sends SIGUSR1 instead of SIGTERM with the force prefix

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221402

            Bug ID: 221402
           Summary: [PATCH] net/haproxy: sends SIGUSR1 instead of SIGTERM
                    with the force prefix
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: demon at FreeBSD.org
          Reporter: fw at moov.de
          Assignee: demon at FreeBSD.org
          Keywords: patch
             Flags: maintainer-feedback?(demon at FreeBSD.org)

Created attachment 185247
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185247&action=edit
patch for net/haproxy

I think there's a bug in the RC script that makes it impossible to use
HAProxy's "hard stop" feature where it *immediately* quits and closes all
established connections.

The RC script always sends the USR1 signal to HAProxy, even if the force prefix
is used (but in this case the TERM signal should be used). That's because the
$rc_force variable is not available in the context. (See /etc/rc.d/bgfsck for
another working example.)

I've attached patches for both net/haproxy and net/haproxy-devel.

-- 
You are receiving this mail because:
You are the assignee for the bug.