[Pkg-haproxy-maintainers] Bug#882610: Please drop haproxy.service-start-after-syslog.patch
Laurent Bigonville
bigon at debian.org
Fri Nov 24 18:22:42 UTC 2017
Source: haproxy
Version: 1.7.9-1
Severity: normal
Hi,
I see in the haproxy.service file that you have a After=/Wants=syslog.service
The installed syslog implementation installed on the machine is always
socket activated so adding After=/Wants=syslog.service is not needed
(and can make the dependency chain more complex).
IMHO, the haproxy.service-start-after-syslog.patch patch should be
dropped.
Do you have any specific reasons to keep this patch?
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
More information about the Pkg-haproxy-maintainers
mailing list