This bug was also filed at <a href="https://bugzilla.redhat.com/process_bug.cgi">https://bugzilla.redhat.com/process_bug.cgi</a> [<a href="https://bugzilla.redhat.com/process_bug.cgi" target="_blank">^</a>]<br />
<br />
Description of problem:<br />
<br />
Although the /etc/init.d/bmc-watchdog script defines a variable named PIDFILE<br />
which points to /var/run/bmc-watchdog.pid when executing the script with the<br />
start parameter, the PIDFILE does not even get created (nor does it contain the<br />
actual PID for that matter).<br />
<br />
At <a href="http://pastebin.com/AMPdPgDP">http://pastebin.com/AMPdPgDP</a> [<a href="http://pastebin.com/AMPdPgDP" target="_blank">^</a>] it is possible to see what I did to make the<br />
script store the PID (lines 44 and 45) inside the PIDFILE. I don't think this<br />
is the correct approach (as I would think that the daemon function that gets<br />
called fron the script should be responsible for storing the PID). Also I would<br />
like to point out that storing the PID is not possible using the bmc-watchdog<br />
utility by itself (it does not have any command-line option for storing the PID<br />
in a PIDFILE).<br />
<br />
Version-Release number of selected component (if applicable):<br />
freeipmi-bmc-watchdog.x86_64 0.7.16-3.el6
↧
