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 cannot always connect > to the LCDd daemon. In VDR's log it shows up like this: > > OK: > > Sep 18 16:31:49 vdrkone2 vdr: [4890] starting plugin: lcdproc > Sep 18 16:31:49 vdrkone2 vdr: connection to LCDd at localhost:13666 > established. > Sep 18 16:31:49 vdrkone2 vdr: LCD output thread started (pid=4890), > display size: 2x16 > > NOT OK: > > Sep 18 19:05:45 vdrkone2 vdr: [4876] starting plugin: lcdproc > Sep 18 19:05:45 vdrkone2 vdr: [4876] stopping plugin: femon > Sep 18 19:05:45 vdrkone2 vdr: [4876] stopping plugin: burn > > Now, the question is, does this really cause VDR to shut down? And if > so, should VDR behave in some other way in such a case? Or is it just > lcdproc plugin that causes such a behaviour? Is it possible for VDR to > retry starting plugin which failed to start? > > -Petri > > > _______________________________________________ > vdr mailing list > vdr@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > Hi, what i now there is a patch inside Extension Patch that allow VDR to start even if a plugin fails. I don't remember which it's, just check inside the package. Diego Pierotto -- Member of the Italian VDR Wiki http://vdr.spaghettilinux.org/ _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
