saslauthd run control script not using OPTIONS from /etc/default/saslauthd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postfix (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I used the ISPConfig tutorial for upgrading my ISPConfig server from Ubuntu 7.10 to 8.04 and things went very well. Except for the final steps of setting up Postfix to work with saslauthd. Here's what I found. If I run saslauthd from the command line, explicitly specifying the -m mux path then things work fine, per the tutorial. If I then run /etc/init.
/etc/init.
++ MECH_OPTIONS=
++ THREADS=5
++ OPTIONS='-c -m /var/spool/
+ '[' yes '!=' yes ']'
+ '[' xpam = x ']'
+ PARAMS=' -a pam'
+ START='--start --quiet --pidfile /var/spool/
+ case "${1}" in
+ echo -n 'Starting SASL Authentication Daemon: '
Starting SASL Authentication Daemon: ++ dpkg-statoverride --list /var/run/saslauthd
+ dir='root sasl 710 /var/run/saslauthd'
+ test -z 'root sasl 710 /var/run/saslauthd'
+ createdir root sasl 710 /var/run/saslauthd
+ '[' -d /var/run/saslauthd ']'
+ mkdir -p /var/run/saslauthd
+ chown -c -h root:sasl /var/run/saslauthd
changed ownership of `/var/run/
+ chmod -c 710 /var/run/saslauthd
mode of `/var/run/
+ start-stop-daemon --start --quiet --pidfile /var/spool/
+ echo saslauthd.
/etc/default/
#
# Settings for saslauthd daemon
# Please read /usr/share/
#
# Should saslauthd run automatically on startup? (default: no)
START=yes
# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"
# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"
# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam -- use PAM
# rimap -- use a remote IMAP server
# shadow -- use the local shadow password file
# sasldb -- use the local sasldb database file
# ldap -- use LDAP (configuration is in /etc/saslauthd.
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="pam"
# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""
# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=5
# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# See /usr/share/
# See the saslauthd man page for general information about these options.
#
# Example for postfix users: "-c -m /var/spool/
#OPTIONS="-c -m /var/run/saslauthd"
OPTIONS="-c -m /var/spool/
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.