Hi all,
Does VDR had exit codes? I mean, how could I find what is the cause of VDR exit?
For example, I want to know is the VDR exit for storage failure, driver failure, timers.conf failure or any thing else.
It is because I wrote a script for restarting my system when vdr exits, but I want to prevent this for errors that are persistent, like hard disk failure, or timers.conf file failure.
Thanks.
J. Anderson.
JikJikMan wrote:
Hi all,
Does VDR had exit codes? I mean, how could I find what is the cause of VDR exit?
For example, I want to know is the VDR exit for storage failure, driver failure, timers.conf failure or any thing else.
It is because I wrote a script for restarting my system when vdr exits, but I want to prevent this for errors that are persistent, like hard disk failure, or timers.conf file failure.
Those are explained in the vdr(1) man-page.
Anssi Hannula wrote:
JikJikMan wrote:
Hi all,
Does VDR had exit codes? I mean, how could I find what is the cause of VDR exit?
For example, I want to know is the VDR exit for storage failure, driver failure, timers.conf failure or any thing else.
It is because I wrote a script for restarting my system when vdr exits, but I want to prevent this for errors that are persistent, like hard disk failure, or timers.conf file failure.
Those are explained in the vdr(1) man-page.
Hi All,
I took a look at vdr man page, but there is only 3 exit codes. and they don't specify what are the exact problems. I think it's a very good idea, to expand this codes, for example if the storage is not accessible, the return code be 5, if there is a error in timers.conf the code would be 6, and so on.
Thanks.
John.
On Tue, 2006-11-07 at 15:44 +0330, JikJikMan wrote:
Hi all,
Does VDR had exit codes? I mean, how could I find what is the cause of VDR exit?
For example, I want to know is the VDR exit for storage failure, driver failure, timers.conf failure or any thing else.
It is because I wrote a script for restarting my system when vdr exits, but I want to prevent this for errors that are persistent, like hard disk failure, or timers.conf file failure.
This topic is quite well covered with man/info pafes + additional README.
Anyway, it _could_ be useful to see if immediate exit code was caused by prim.dev or pluigin in case of fatal error ?
(just thinking abt my init.d scripts - it is clearly different if net is down, ex, for full house elecrity net-halt+init? I never reload - maybe drivers for vdr restart are useful some users, for me UPS handles all minor problems (including "soft" powerdown), I'd think it might be just for 100% overkill to have any net-reboot - so ,it could be usefuyl to disable exit if currewnt ch is unencryptable ?)
- Petri
-
Anssi Hannula -
JikJikMan -
Petri Hintukainen