The -m parameter is used to define the folder where the saslauthd.pid will be created :)
See the man page : -m path Use path as the pathname to the named socket to listen on for connection requests. This must be an absolute pathname, and MUST NOT include the trailing "/mux". Note that the default for this value is "/var/state/saslauthd" (or what was specified at compile time) and that this directory must exist for saslauthd to function. Bug report filed, by email. I'll update here when i'll hear back from them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/2098601 Title: saslauthd.service should take PIDFile path from /etc/default/saslauthd Status in cyrus-sasl2 package in Ubuntu: Incomplete Bug description: * Context : Ubuntu 24.04 sasl2-bin 2.1.28+dfsg1-5ubuntu3.1 * saslauthd.service has a fixed path in its file : PIDFile=/var/run/saslauthd/saslauthd.pid * But, in /etc/default/saslauthd, if you have postfix running chroot, the pid path will differ : OPTIONS="-c -m /var/spool/postfix/run/saslauthd -r" * With different paths for the file, saslauthd won't be able to start : saslauthd.service: Can't open PID file /run/saslauthd/saslauthd.pid (yet?) after start: No such file or directory saslauthd.service should take PIDFile from /etc/default/saslauthd (orthe opposite) and /etc/default/saslauthd should clearly explain what need to be done if you set a different path for the pid file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2098601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
