Description of problem:
Although the /etc/init.d/bmc-watchdog script defines a variable named PIDFILE
which points to /var/run/bmc-watchdog.pid when executing the script with the start parameter, the PIDFILE does not even get created (nor does it contain the actual PID for that matter).
At http://pastebin.com/AMPdPgDP it is possible to see what I did to make the script store the PID (lines 44 and 45) inside the PIDFILE. I don't think this is the correct approach (as I would think that the daemon function that gets called fron the script should be responsible for storing the PID). Also I would like to point out that storing the PID is not possible using the bmc-watchdog utility by itself (it does not have any command-line option for storing the PID in a PIDFILE).
Version-Release number of selected component (if applicable):
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
As proposed in the message from the RHEL Product and Program Management I would like to have this feature scheduled to be released as soon as possible. Could you please look into this and take this request further down the road?
Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
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.