This is the debian change: --- a/debian/sasl2-bin.saslauthd.service +++ b/debian/sasl2-bin.saslauthd.service @@ -5,9 +5,7 @@ Documentation=man:saslauthd(8) [Service] Type=forking Group=sasl -PIDFile=/var/run/saslauthd/saslauthd.pid -EnvironmentFile=/etc/default/saslauthd -ExecStart=/usr/sbin/saslauthd -a $MECHANISMS $MECH_OPTIONS $OPTIONS -n $THREADS +ExecStart=/bin/bash -c '. /etc/default/saslauthd; exec /usr/sbin/saslauthd -a $MECHANISMS $MECH_OPTIONS $OPTIONS -n $THREADS' RuntimeDirectory=saslauthd
[Install] To me that is identical to just dropping PIDFile, i.e: --- a/debian/sasl2-bin.saslauthd.service +++ b/debian/sasl2-bin.saslauthd.service @@ -5,7 +5,6 @@ Documentation=man:saslauthd(8) [Service] Type=forking Group=sasl -PIDFile=/var/run/saslauthd/saslauthd.pid EnvironmentFile=/etc/default/saslauthd ExecStart=/usr/sbin/saslauthd -a $MECHANISMS $MECH_OPTIONS $OPTIONS -n $THREADS RuntimeDirectory=saslauthd The exec() in the former diff just makes it replace bash, which was used for variable expansion. But we get the same variable expansion behavior by keeping EnvironmentFile above. Let me do some tests with postfix in noble, where it's still chrooted. It's annoying that saslauthd has no option to run in the foreground, in which case we could use Type=simple instead of forking. But systemd seems to be handling Type=forking without a PIDFile just fine in the quick testing I did. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098601 Title: saslauthd.service should take PIDFile path from /etc/default/saslauthd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2098601/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
