Hi,
Testing 1.3.27 runs fine, zaps fast etc etc then this morning I find it has tried restarting during the night.
mar jui 19 00:18:09 CEST 2005 Password:
No recording was planned. Other software running - vdradmin 0.97-am3.3 and Evolution.
Ideas?
Cheers
Tony
Testing 1.3.27 runs fine, zaps fast etc etc then this morning I find it has tried restarting during the night.
mar jui 19 00:18:09 CEST 2005 Password:
No recording was planned. Other software running - vdradmin 0.97-am3.3 and Evolution.
Ideas?
VDR has no passwords. Sounds like you machine rebooted and are stopping in the normal user login. If you machine does not start vdr automaticly in the background it will just stay sitting there idle forever.
May be you have shutdown in vdr enabled, so your machine tried/did shutting down after being idle.
regards Peter P.S. most bugs walk on two legs and are sitting in front of the screen ;-)
Le mercredi 20 juillet 2005 à 09:41 +0200, Peter Dittmann a écrit :
Testing 1.3.27 runs fine, zaps fast etc etc then this morning I find
it
has tried restarting during the night.
mar jui 19 00:18:09 CEST 2005 Password:
No recording was planned. Other software running - vdradmin
0.97-am3.3
and Evolution.
Ideas?
VDR has no passwords.
I use runvdr script, it has a password
Sounds like you machine rebooted and are stopping in the normal user login.
No it did it again yesterday at 18:39 I was near the machine and it did not shut down.
If you machine does not start vdr automaticly in the background it will just stay sitting there idle forever.
No it is started manually but usually runs for weeks without being shut down.
May be you have shutdown in vdr enabled, so your machine tried/did shutting down after being idle.
Using same configuration files since VDR 1.3.14
regards Peter P.S. most bugs walk on two legs and are sitting in front of the screen ;-)
This is new behavior. It has never done this before.
Cheers
Tony
tony tony@tgds.net wrote:
Le mercredi 20 juillet 2005 à 09:41 +0200, Peter Dittmann a écrit :
P.S. most bugs walk on two legs and are sitting in front of the screen ;-)
The layer 8 problem...
This is new behavior. It has never done this before.
Sure, but since this happens _before_ vdr is started (if I got it right, otherwise a password prompt wouldn't make too much sense) the problem is unrelated to vdr.
You may want to post your start script instead of keeping us in the dark...
Le mercredi 20 juillet 2005 à 22:46 +0200, Harald Milz a écrit :
This is new behavior. It has never done this before.
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
You may want to post your start script instead of keeping us in the dark...
It is called "runvdr" and is found in the same folder as vdr... =:-D Yes mine is modified to include export LANG=fr_FR
I have traced the problem to epg.data.
Tony
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
Le vendredi 22 juillet 2005 à 16:02 +0200, Peter Dittmann a écrit :
This is new behavior. It has never done this before.
Lucky guy ;-)
You saw photos of my girlfriend? =:-D
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.
I quote: # Since this script loads the DVB driver, it must be started # as user 'root'.
Please tell me how to run runvdr without needing the root password.
Tony
tony wrote:
I quote: # Since this script loads the DVB driver, it must be started # as user 'root'.
Please tell me how to run runvdr without needing the root password.
man sudo man visudo man sudoers
Bye
-
Harald Milz -
Luca Olivetti -
Peter Dittmann -
tony