Date: Thu, 10 Aug 2017 21:56:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 221402] [PATCH] net/haproxy: sends SIGUSR1 instead of SIGTERM with the force prefix Message-ID: <bug-221402-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221402 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@FreeBSD.org Reporter: fw@moov.de Assignee: demon@FreeBSD.org Keywords: patch Flags: maintainer-feedback?(demon@FreeBSD.org) Created attachment 185247 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D185247&action= =3Dedit 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 pr= efix is used (but in this case the TERM signal should be used). That's because t= he $rc_force variable is not available in the context. (See /etc/rc.d/bgfsck f= or another working example.) I've attached patches for both net/haproxy and net/haproxy-devel. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221402-13>