>> > This is new behavior. It has never done this before. Lucky guy ;-) The comunity has almost resigned to expect more than some days without an unexpected vdr restart. >> >> Sure, but since this happens _before_ vdr is started (if I got it right, > > No, wrong. Stopping in the night has nothing to do with _before_ > starting. Stopping is _after_ starting There are a lot of possible causes that can trigger a vdr restart. 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). However it's the job of "runvdr" to insure to get vdr cleanly restarted automaticly after an emergency exit. If you put a password into runvdr you didn't realy understood what runvdr's job and spoided the error recovery done by runvdr. So if you expect vdr to run for some weeks you have to allow vdr to recover using runvdr without a password needed. 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. regards Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.linuxtv.org/pipermail/vdr/attachments/20050722/aad79b96/attachment.htm
