Description of problem: On logout of current rawhide, I notice restorecond fails to stop. It also fails to stop when issued the command 'service restorecond stop'. This is because the pid in /var/run/restorecond.pid is one less than the actual pid, so the killproc() function in /etc/init.d/functions can't find the pid to kill. [root@osprey ~]# cat /var/run/restorecond.pid 2302 [root@osprey ~]# ps -ef | grep restorecond | grep -v grep root 2303 1 0 21:35 ? 00:00:00 /usr/sbin/restorecond Hand editing /var/run/restorecond.pid to make the value match the running pid results in a successful stop. One result of this problem is a new restorecond for every 'service restorecond restart' invocation, since the 'stop' fails and the 'start' succeeds. Version-Release number of selected component (if applicable): policycoreutils-1.30.17-2 How reproducible: Every time. Steps to Reproduce: 1. Run 'service restorecond stop' 2. 3. Actual results: [root@osprey ~]# service restorecond stop Shutting down restorecond: [FAILED] Expected results: [root@osprey ~]# service restorecond stop Shutting down restorecond: [OK] Additional info:
I have no idea how I managed to generate two of these bug reports. Please mark 199045 as a duplicate of 199044 (or vice versa). Sorry.
Fixed in policycoreutils-1.30.17-4
Please ignore comment #1. I'm a moron and I have visions of duplicate bugzillas where there aren't any. A new day brings fresh clarity.
Verified fixed for me. [root@osprey ~]# rpm -q policycoreutils policycoreutils-1.30.17-4 [root@osprey ~]# service restorecond restart Shutting down restorecond: [ OK ] Starting restorecond: [ OK ] [root@osprey ~]# Thanks!