Out of curiosity, have you looked into using the RedHat function lib to start and stop the service? It has intelligence to check for the PID file and a running PID so you don't run into these lock file issues. <br><br>
Dan<br><br><div class="gmail_quote">On Wed, Mar 16, 2011 at 1:36 PM, Bruce Ediger <span dir="ltr"><<a href="mailto:bediger@stratigery.com">bediger@stratigery.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, 16 Mar 2011, Dan Kulinski wrote:<br>
<br>
> I apologize, I messed up my explanation on a critical part of this. K<br>
> scripts are also run when entering that runlevel, not at exit. You want to<br>
> have your K script in the shutdown runlevel (runlevel 0) and the reboot<br>
> level (runlevel 6).<br>
<br>
</div>OK, that's what I thought from reading the /etc/rc.d/rc script, but<br>
there's so much gibberish about Red Hat init scripts out on the web that<br>
I felt like I had to double check somewhere reliable.<br>
<br>
I still can't tell why the script has 4 'S'-script links, and no<br>
'K'-script link, but the lack of a 'K'-script explains why the lockfile<br>
existed through the shutdown and reboot. /etc/rc.d/rc0.d/K97script.sh<br>
never got called, and that's the place where lockfile deletion happens.<br>
<div><div></div><div class="h5">_______________________________________________<br>
clue mailing list<br>
<a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br>