Package: zabbix-agent2 Version: 1:7.0.9+dfsg-1 Severity: normal Dear Maintainer,
thank you for handling my last bug report regarding the PID location. Unfortunately upstream also violates the FHS in regard to the placement of sockets. By default it sets ControlSocket to /tmp/agent.sock and PluginSocket to /tmp/agent.plugin.sock (although the latter is not activated by default). Both locations violate the FHS, which would place them under /run/zabbix/ Thank you and kind regards Dan -- System Information: Debian Release: 12.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-30-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zabbix-agent2 depends on: ii adduser 3.134 ii init-system-helpers 1.65.2 ii libc6 2.36-9+deb12u9 ii libpcre2-8-0 10.42-1 ii libsqlite3-0 3.40.1-2+deb12u1 ii libssl3 3.0.15-1~deb12u1 ii sysvinit-utils [lsb-base] 3.06-4 ii zlib1g 1:1.2.13.dfsg-1 zabbix-agent2 recommends no packages. Versions of packages zabbix-agent2 suggests: ii logrotate 3.21.0-1
