[vdr] Re: Error handling vs. user friendliness.

[Gavin Hamill <gdh@acentral.co.uk>]

On Mon, Jan 03, 2005 at 12:22:56AM +0100, Josef Wolf wrote:
> Hello!
> 
> Am I the only one who finds VDR's error handling strategies somewhat
> inconvenient?  Here are some examples:
> 
> - VDR refuses to start up when some programmed recording timer refers to
>   an unknown channel.  I stumbled over this when I programmed a short
>   test recording and reorganized channels.conf thereafter.

Yes! I ended up deleting everything in /root/vdr-1.x.x, recompiling and still
getting the same error, only to find it was a problem with timers.conf

I noticed no useful messages in syslog! :(
 
> - VDR refuses to start up when there are "duplicated data" in channels.conf.
>   What is the reason for this restriction?  Why can't I have a program
>   multiple times in channels.conf?  Or why not to just ignore duplicated
>   entries?

That's useful to know, I wasn't aware of that one. Esp. useful on a system
like mine where I get maybe 12 hours of EPG live in the DVB stream, but also
import 14 days via external script / SVDRP.
 
> - Streamdev-server restarts VDR when one of the clients fails to keep up
>   with the data rate.  The effect is that all clients and recordings are
>   interrupted.  Why not just kick off the offending client and keep
>   running?

Well, that's hardly VDR's problem... I have so many problems with the streamdev
plugin :(
 
Cheers,
Gavin.