Red Hat Bugzilla – Bug 438340
lock files are badly handled by all init scripts
Last modified: 2014-01-12 19:07:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:126.96.36.199) Gecko/20080208 Fedora/188.8.131.52-1.fc8 Firefox/184.108.40.206
Description of problem:
There are more mistakes in those init scripts:
1. Lock files are created in function start() but they are not removed in function stop().
2. The existence of a lock file is never tested, so daemons could be run multiple times.
3. /etc/init.d/<script> condrestart does nothing, because "[ -d $lockfile ]" tests the existence of a directory. But lock file is not a directory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. look into /etc/init.d/iprdump
2. look into /etc/init.d/iprinit
3. look into /etc/init.d/iprupdate
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
These are also relatively easy to clean up. Giving it a devel-ack.
Init scripts have been fixed in the iprutils-2.2.8-2.el4 build, which has been
tagged and built. Moving bug to MODIFIED.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.