Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53158 - [dev-libs/cyrus-sasl-2.1.14] /etc/conf.d/saslauthd: -n ${VAR} fails due to missing quoting marks
Summary: [dev-libs/cyrus-sasl-2.1.14] /etc/conf.d/saslauthd: -n ${VAR} fails due to mi...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Net-Mail Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-06 13:40 UTC by Alexander Papaspyrou
Modified: 2004-08-25 17:01 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Fix for the stated bug (saslauthd.conf.diff,564 bytes, patch)
2004-06-06 13:44 UTC, Alexander Papaspyrou
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Papaspyrou 2004-06-06 13:40:10 UTC
When trying to start /etc/init.d/saslauthd, it always complains about an invalid option ("-H"), even if the corresponding variable ($SASL_RIMAP_HOSTNAME in /etc/conf.d/saslauthd) is unset.

The problem, however lies in the small "variable collection" script at the end of /etc/conf.d/saslauthd):

The tests in /etc/conf.d/saslauthd (line 1{4,6,8}) whether the variables are not null always return "true" due to missing quoting marks (${VAR} instead of "${VAR}"). Thus, /etc/init.d/saslauthd complains when any of the three variables is undefined.

Reproducible: Always
Steps to Reproduce:
1. Install dev-libs/cyrus-sasl-2.1.14
2. Comment out the second and the third variable in /etc/conf.d/saslauthd
3. Try to run /etc/init.d/saslauthd
Actual Results:  
/etc/init.d/saslauthd complains and displays the help message.

Expected Results:  
/etc/init.d/saslauthd should start silently.

[ ~ ]
host # emerge --info
Portage 2.0.50-r7 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-hardened-r3)
=================================================================
System uname: 2.6.5-hardened-r3 i686 Intel(R) Celeron(R) CPU 2.40GHz
Gentoo Base System version 1.4.15
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -fstack-protector"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer -fstack-protector"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox userpriv usersandbox"
GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror      
          http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="acl acpi apache2 apm berkdb caps crypt imap ldap maildir mmx mpi ncurses
nls pam readline sse ssl tcpd x86 xml2 zlib"
Comment 1 Alexander Papaspyrou 2004-06-06 13:44:46 UTC
Created attachment 32798 [details, diff]
Fix for the stated bug
Comment 2 Romang 2004-06-10 06:12:28 UTC
[root@zataz conf.d]$cat attachment.cgi\?id\=32798 | patch -p1
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- saslauthd.conf.orig        2004-03-04 19:39:04.000000000 +0100
|+++ saslauthd.conf.patched     2004-06-06 22:27:21.975151315 +0200
--------------------------
File to patch: saslauthd
patching file saslauthd
[root@zataz conf.d]$vi saslauthd 
[root@zataz conf.d]$rm attachment.cgi\?id\=32798 
[root@zataz conf.d]$/etc/init.d/saslauthd start
 * WARNING:  "saslauthd" has already been started.
[root@zataz conf.d]$/etc/init.d/saslauthd zap  
 * Manually resetting saslauthd to stopped state.
[root@zataz conf.d]$/etc/init.d/saslauthd start
 * Starting saslauthd...
/usr/sbin/saslauthd: invalid option -- T
usage: saslauthd [options]

option information:
  -a <authmech>  Selects the authentication mechanism to use.
  -c             Enable credential caching.
  -d             Debugging (don't detach from tty, implies -V)
  -O <option>    Optional argument to pass to the authentication
                 mechanism.
  -l             Disable accept() locking. Increases performance, but
                 may not be compatible with some operating systems.
  -m <path>      Alternate path for the saslauthd working directory,
                 must be absolute.
  -n <procs>     Number of worker processes to create.
  -s <kilobytes> Size of the credential cache (in kilobytes)
  -t <seconds>   Timeout for items in the credential cache (in seconds)
  -v             Display version information and available mechs
  -V             Enable verbose logging
                 authentication mechanisms and exit.
  -h             Dispaly this message.

saslauthd 2.1.14
authentication mechanisms: getpwent pam rimap shadow
                                                                                                                                                                 [ ok ]
[root@zataz conf.d]

And yet the -T option ....
Comment 3 Tuan Van (RETIRED) gentoo-dev 2004-08-25 17:01:07 UTC
I believe this is not applicable to the latest stable version in portage. Closing.