<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br>
<br><font size=2><tt>>> > This is new behavior. It has never done
this before.<br>
Lucky guy ;-)</tt></font>
<br><font size=2><tt>The comunity has almost resigned to expect more than
some days without an unexpected vdr restart.</tt></font>
<br>
<br><font size=2><tt>>> <br>
>> Sure, but since this happens _before_ vdr is started (if I got
it right,<br>
><br>
> No, wrong. Stopping in the night has nothing to do with _before_<br>
> starting. Stopping is _after_ starting<br>
</tt></font>
<br><font size=2><tt>There are a lot of possible causes that can trigger
a vdr restart.</tt></font>
<br><font size=2><tt>This is the way it's supposed to do it as a watchdog
and there is nothing wrong if it's not happening too frequently or completely
recreatable because of broken code (it's undesirable anyway). </tt></font>
<br>
<br><font size=2><tt>However it's the job of "runvdr" to insure
to get vdr cleanly restarted automaticly after an emergency exit.</tt></font>
<br><font size=2><tt>If you put a password into runvdr you didn't realy
understood what runvdr's job and spoided the error recovery done by runvdr.</tt></font>
<br><font size=2><tt>So if you expect vdr to run for some weeks you have
to allow vdr to recover using runvdr without a password needed.</tt></font>
<br>
<br><font size=2><tt>EPG scan is known to be critical. Once it does a lot
of channel switching. Second it may tune to critical channels (e.g. HDTV
does not work with a full featured card). And third EPG is quite often
containing horrible things that crash vdr.</tt></font>
<br>
<br><font size=2><tt>regards Peter</tt></font>
<br>
<br>