Bug 104671

Summary: lock file not removed when stopped with the rc-script
Product: [Retired] Red Hat Linux Reporter: Jeffrey C. Davis <jdavis>
Component: spamassassinAssignee: Chip Turner <cturner>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:58:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeffrey C. Davis 2003-09-18 18:04:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; RA; T312461)

Description of problem:
The lock file used in the rc-script (/etc/init.d/spamassassin) does not match 
betwen the 'start', 'stop', and 'condrestart' options.  'start' creates the 
incorrect file /var/lock/subsys/spamd and 'stop' tries to remove the 
file /var/lock/subsys/spamassassin.  The lock file is never removed when 
spamassassin is stopped with the rc-script.  Additionally, the 'condrestart' 
option will never work, because it looks for the 
file /var/lock/subsys/spamassassin.


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

How reproducible:
Always

Steps to Reproduce:
1. # /etc/init.d/spamassassin start
2. # ls /var/lock/subsys
     (notice the spamd file)
3. # /etc/init.d/spamassassin stop
4. # ls /var/lock/subsys
     (notice the spamd file is still there)


Actual Results:  The file /var/lock/subsys/spamd is created (touched) but never 
is removed.


Expected Results:  The file /var/lock/subsys/spamassassin should be created 
(touched) when the rc-script is given the 'start' option, nad should be removed 
when given the 'stop' option.


Additional info:

Comment 1 Warren Togami 2004-02-29 06:19:10 UTC

*** This bug has been marked as a duplicate of 88110 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:58:38 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.