<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 10:36 AM, George Galt <span dir="ltr"><<a href="mailto:george.galt@gmail.com" target="_blank">george.galt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div class="h5"><br><div class="gmail_extra">
<span style="color:rgb(34,34,34)">In defense of process monitors, I run one not because myth is unreliable, but because it is so reliable that it may take several days or more before I notice it isn't running -- by which time I've missed a few of my wife's favorite programs. Since I don't watch TV every night (or sometimes for more than a week, even when home), I can't otherwise monitor the system. Do you have any other suggestions if a process monitor isn't the preferred strategy?</span><br>
</div></div></div><span class=""><font color="#888888"><div class="gmail_extra"><span style="color:rgb(34,34,34)"></span></div></font></span></div></blockquote><div><br></div><div><br></div><div>I'm right there with you on status monitors. I run one too, for the same reason. But I'll make a suggestion. Have your script email you went it does do a restart. That way, if you make sure a mistake like you just did, you will discover it relatively quickly. In addition, if anything ever does start going haywire with your system (like it needs to restart every day), you'll be clued in that something is going wrong instead of having it hidden from you.</div>
<div> </div></div><br clear="all"><div>-- <br></div>Ron Frazier
</div></div>