Red Hat Bugzilla – Bug 85189
Spassassin init script blocks when run
Last modified: 2008-05-01 11:38:05 EDT
Description of problem:
When you run the command "/sbin/service spamassassin start" the spamd process
is started but the service command never returns control to the shell.
On further investigation it looks like the script /etc/init.d/spamassassin tests
for the existance of the file /etc/sysconfig/spamassassin and if it exists it
sources this file. If the file does not exist then the init script assigns some
default values to the variable $OPTIONS. These defaults include the "-d" flag
to run the spamd process as a daemon. $OPTIONS is passed to the spamd process
on line 35 of the init script.
The problem is that the file /etc/sysconfig/spamassassin exists by default, but
uses the variable name $SPAMDOPTIONS rather than $OPTIONS. This means that the
spamd process is never passed any options, and hence blocks rather than
The fix would appear to be to use consistent variable names across the two
files: /etc/init.s/spamassassin and /etc/sysconfig/spamassassin.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run the command "/sbin/service spamassassin start"
2. wait for control to return
3. keep waiting, and waiting......
Control never returns to shell from which the spamassassin init script is launched.
The spamd process should be run with the "-d" flag so that control returns to
the shell when the init script is run.
*** This bug has been marked as a duplicate of 84445 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.