Bug 88110 - Spamassassin init script sets wrong subsys flag
Spamassassin init script sets wrong subsys flag
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: spamassassin (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
:
: 104671 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-05 15:45 EST by Brian Landers
Modified: 2007-04-18 12:52 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-24 17:37:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brian Landers 2003-04-05 15:45:23 EST
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 08:57:04 EDT
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 09:11:49 EDT
this should be fixed in spamassassin-2.50-4.8.x.i386.rpm, which is in rawhide
Comment 3 Warren Togami 2004-02-29 01:19:11 EST
*** Bug 104671 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.