]> git.kaiwu.me - haproxy.git/commit
projects / haproxy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 709cde6) | patch
BUG/MINOR: mworker: wrong signals during startup
authorWilliam Lallemand <wlallemand@haproxy.com>
Tue, 18 Nov 2025 09:23:13 +0000 (10:23 +0100)
committerWilliam Lallemand <wlallemand@haproxy.com>
Tue, 18 Nov 2025 09:27:34 +0000 (10:27 +0100)
commit9bf01a0d296b6f1a4de4f932ae8e7f250a58fa25
treeb86c6b93b060c7b7cf8aadd639c98fc8479393f3tree | snapshot
parent709cde6d0877f409173d81dd46e1d0f52af92279commit | diff
BUG/MINOR: mworker: wrong signals during startup

Since the new master-worker model in 3.1, signals are registered in
step_init_3(). However, those signals were supposed to be registered
only for the worker or the standalone mode. It would call the wrong
callback in the master even during configuration parsing.

The patch set the signals handler to NULL for the master so it does
nothing until they really are registered.

Must be backported as far as 3.1.
src/haproxy.c diff | blob | history
haproxy upstream