Bug 698705

Summary:	rsyslog creates invalid subsys lock file
Product:	Red Hat Enterprise Linux 6	Reporter:	Tomas Heinrich <theinric>
Component:	rsyslog	Assignee:	Tomas Heinrich <theinric>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2	CC:	daniel, ksrot, pvrabec, theinric
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	650509	Environment:
Last Closed:	2011-12-06 16:51:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	650509
Bug Blocks:

Description Tomas Heinrich 2011-04-21 14:53:37 UTC

Version-Release number of selected component (if applicable):
rsyslog-4.6.2-3.el6

+++ This bug was initially created as a clone of Bug #650509 +++

Description of problem:
rsyslog's initscript creates a lock file named rsyslogd. The initscript's name is rsyslog, and because these two don't match, rc will not run the stop action when shutting down the system.

Version-Release number of selected component (if applicable):
rsyslog-3.22.1-3.el5
rsyslog-4.4.2-6.fc13.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot with rsyslog enabled
2. Check /var/lock/subsys

Comment 3 Karel Srot 2011-08-16 15:43:15 UTC

Since lockfile is changed also /etc/init.d/rsyslog should be updated with:

rhstatus() {
        status -p "${PIDFILE}" -l $prog $prog
}

Comment 6 errata-xmlrpc 2011-12-06 16:51:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1673.html