Bug 88110

Summary: Spamassassin init script sets wrong subsys flag
Product: [Retired] Red Hat Linux Reporter: Brian Landers <brian>
Component: spamassassinAssignee: Warren Togami <wtogami>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: jdavis, matthew, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-24 21:37:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brian Landers 2003-04-05 20:45:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
In the init script for spamassassin (spamd), the "start" option touches the
subsys flag "spamd" but the "stop", and "condrestart" options look for the flag
"spamassassin"

  start)
        ...
        [ $RETVAL = 0 ] && touch /var/lock/subsys/spamd

  stop)
        ...
        [ $RETVAL = 0 ] && rm -f /var/lock/subsys/spamassassin

  condrestart)
        [ -e /var/lock/subsys/spamassassin ] && $0 restart



Version-Release number of selected component (if applicable):
spamassassin-2.44-11.8.x

How reproducible:
Always

Steps to Reproduce:
1. edit /etc/init.d
2. observe that the subsys flags are different
    

Additional info:

Comment 1 Matthew Lenz 2003-04-07 12:57:04 UTC
I've got the same problem.  Going into runlevel 1 (# init 1) leaves spamassissin
running and when returning (# exit) to the previous runlevel (in my case 5)
spamassissin fails to start because it is already running.

Comment 2 Chip Turner 2003-04-07 13:11:49 UTC
this should be fixed in spamassassin-2.50-4.8.x.i386.rpm, which is in rawhide

Comment 3 Warren Togami 2004-02-29 06:19:11 UTC
*** Bug 104671 has been marked as a duplicate of this bug. ***