Package: sasl2-bin
Version: 2.1.28+dfsg1-9
Followup-For: Bug #1110309
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
After upgrading to trixie I get this error in saslauthd logs
Feb 27 13:15:29 comms-staging systemd[1]:
/usr/lib/systemd/system/saslauthd.service:8: PIDFile= references a path below
legacy directory /var/run/, updating /var/run/saslauthd/saslauthd.pid →
/run/saslauthd/saslauthd.pid; please update the unit file accordingly.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to set the path in /etc/saslauthd and in
/etc/systemd/system/saslauthd.service.d/override.conf to
/var/spool/postfix/run/saslauthd/saslauthd.pid
[Service]
PIDFile=/var/spool/postfix/run/saslauthd/saslauthd.pid
* What was the outcome of this action?
But ldap authentication failed and I had to switch it back to
/var/spool/postfix/var/run/saslauthd/saslauthd.pid
* What outcome did you expect instead?
I think /run/saslauthd should work or systemd should not give this warning.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.8+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sasl2-bin depends on:
pn db-util <none>
ii debconf [debconf-2.0] 1.5.91
ii init-system-helpers 1.69
ii libc6 2.42-11
ii libcrypt1 1:4.4.38-1
ii libdb5.3t64 5.3.28+dfsg2-9
ii libkrb5-3 1.21.3-5
ii libldap2 2.6.10+dfsg-1
ii libpam0g 1.7.0-5
ii libsasl2-2 2.1.28+dfsg1-9
ii libssl3t64 3.5.3-1
sasl2-bin recommends no packages.
sasl2-bin suggests no packages.
