[Bug 79371] Re: saslauthd init script does not allow movement of PID
I think this is already fixed... With the current version (in Lucid), you can't set PWDIR in the defaults file, its derived from the -m option. Then the following bit of code ensures the directory is created with the right rights: if dpkg-statoverride --list $RUN_DIR /dev/null; then createdir `dpkg-statoverride --list $RUN_DIR` else createdir root sasl 710 $RUN_DIR fi Please reopen if you can reproduce with current lucid. ** Changed in: cyrus-sasl2 (Ubuntu) Status: Confirmed = Fix Released ** Changed in: server-papercuts Status: Confirmed = Fix Released -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
I think this is already fixed... With the current version (in Lucid), you can't set PWDIR in the defaults file, its derived from the -m option. Then the following bit of code ensures the directory is created with the right rights: if dpkg-statoverride --list $RUN_DIR /dev/null; then createdir `dpkg-statoverride --list $RUN_DIR` else createdir root sasl 710 $RUN_DIR fi Please reopen if you can reproduce with current lucid. ** Changed in: cyrus-sasl2 (Ubuntu) Status: Confirmed = Fix Released ** Changed in: server-papercuts Status: Confirmed = Fix Released -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: cyrus-sasl2 (Ubuntu) Assignee: Ubuntu Server Team (ubuntu-server) = (unassigned) ** Changed in: server-papercuts Milestone: lucid-beta-1 = lucid-beta-2 -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: server-papercuts Milestone: None = lucid-beta-1 -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: server-papercuts Milestone: None = lucid-beta-1 -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: server-papercuts Importance: Undecided = Medium ** Changed in: server-papercuts Status: New = Confirmed -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: server-papercuts Importance: Undecided = Medium ** Changed in: server-papercuts Status: New = Confirmed -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Also affects: server-papercuts Importance: Undecided Status: New -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Also affects: server-papercuts Importance: Undecided Status: New -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
There is an undocumented option to imapd.conf ``sasl_saslauthd_path'' which instructs the daemon to look in a non-standard location for the socket. I've opened a bug upstream with the Cyrus maintainers. Perhaps Ubuntu should update the imapd and imap.conf manpages to reflect this useful option? -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
There is an undocumented option to imapd.conf ``sasl_saslauthd_path'' which instructs the daemon to look in a non-standard location for the socket. I've opened a bug upstream with the Cyrus maintainers. Perhaps Ubuntu should update the imapd and imap.conf manpages to reflect this useful option? -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: cyrus-sasl2 (Ubuntu) Assignee: Martin Pitt (pitti) = Ubuntu Server Team (ubuntu-server) Status: In Progress = Confirmed -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
At the end of /etc/defaults/saslauthd I added SYMLINK=/var/run/saslauthd and in the initscript I added this before the createdir function: #bug https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/79371 quickfix test -h $SYMLINK || ln -s $RUN_DIR $SYMLINK the initscript will automagically create the $RUN_DIR by parsing the -m option if specified in $OPTIONS -- saslauthd init script does not allow movement of PID https://bugs.launchpad.net/bugs/79371 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: cyrus-sasl2 (Ubuntu) Status: Unconfirmed = In Progress -- saslauthd init script does not allow movement of PID https://launchpad.net/bugs/79371 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
NOTE: I found yesterday also that as Cyrus-IMAP requires the socket to be located in /var/run/saslauthd/ , and would seem that you can not tell Cyrus-IMAP where to look for the socket (I am yet to 100% confirm this), that I had to make a symlink to the location where my socket was. Also as on reboots the symlink gets destroyed, I added the following two lines to my /etc/init.d/saslauthd script: At the top in the variables section I added: SYMLINK=/var/run/saslauthd after the test to create the socket directory (as stated above), I added the following line: test -h $SYMLINK || ln -s $PWDIR $SYMLINK Hope this information is of use to you guys. -- saslauthd init script does not allow movement of PID https://launchpad.net/bugs/79371 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79371] Re: saslauthd init script does not allow movement of PID
** Changed in: cyrus-sasl2 (Ubuntu) Importance: Undecided = Low Assignee: (unassigned) = Martin Pitt -- saslauthd init script does not allow movement of PID https://launchpad.net/bugs/79371 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
