Jouni Karvo wrote:
Petri Helin wrote:
really causes VDR to not start also. My aim really was to start some
discussion on whether that should be changed. I myself think that VDR
should start although some plugin fails to start. I'd hate to find out
that some timed recording failed because
I like that VDR won't load if a plugin failed. That means there was a
problem, and I should go fix it. Also, it's the plugins job to
continue on non-fatal errors, not VDR. How would VDR even know whats
a non-fatal error for a certain plugin? From VDR's perspective either
the plugin is working
VDR User wrote:
I like that VDR won't load if a plugin failed. That means there was a
problem, and I should go fix it. Also, it's the plugins job to
continue on non-fatal errors, not VDR. How would VDR even know whats
a non-fatal error for a certain plugin? From VDR's perspective either
On Fri, Sep 19, 2008 at 8:20 AM, Petri Helin [EMAIL PROTECTED] wrote:
But why should even a fatal error (from plugin's perspective) cause VDR
to not start? It should only cause the plugin not to be loaded. Of
course plugins could also implement more intelligent initialization and
try to deal
On 09/19/08 17:20, Petri Helin wrote:
VDR User wrote:
I like that VDR won't load if a plugin failed. That means there was a
problem, and I should go fix it. Also, it's the plugins job to
continue on non-fatal errors, not VDR. How would VDR even know whats
a non-fatal error for a certain
VDR User wrote:
I think it's a huge assumption (and incorrect one) to say the main
function of VDR is to record tv shows. I know many people who use it
for watching live tv, email notices, weather report, playing other
media something like an htpc, etc.
Ok, let me rephrase it: for my
So, if a plugin thinks VDR can well run without it, it should just
return true. If it's a plugin that's absolutely necessary for operation,
it shall return false upon failure. VDR can't know that by itself.
Maybe all plugins could have a setting on failure terminate vdr ?
Then the user could
Petri Helin wrote:
In fact I am already wondering why plugins are not
hot-pluggable...
They are, to some degree, by using the proxy plugin. The proxy plugin
can delay loading a plugin, and for some plugins it can unload a plugin
while VDR is running. It can also do the requested
Udo Richter wrote:
Petri Helin wrote:
In fact I am already wondering why plugins are not
hot-pluggable...
They are, to some degree, by using the proxy plugin. The proxy plugin
can delay loading a plugin, and for some plugins it can unload a plugin
while VDR is running. It can also do
Hi,
I have been running VDR as a daemon started via init script for some
years now. I am currently using version 1.6.0-2. The problem is, that
every now and then VDR doesn't start when I boot the server. The culprit
seems to be lcdproc plugins, which for some reason cannot always connect
to the
Petri Helin ha scritto:
Hi,
I have been running VDR as a daemon started via init script for some
years now. I am currently using version 1.6.0-2. The problem is, that
every now and then VDR doesn't start when I boot the server. The culprit
seems to be lcdproc plugins, which for some reason
Diego Pierotto wrote:
Petri Helin ha scritto:
Hi,
I have been running VDR as a daemon started via init script for some
years now. I am currently using version 1.6.0-2. The problem is, that
every now and then VDR doesn't start when I boot the server. The culprit
seems to be lcdproc plugins,
Petri Helin wrote:
really causes VDR to not start also. My aim really was to start some
discussion on whether that should be changed. I myself think that VDR
should start although some plugin fails to start. I'd hate to find out
that some timed recording failed because the lcd display of
13 matches
Mail list logo
