On 20 October 2010 17:02, Rolf Ahrenberg wrote:
>
> On Wed, 20 Oct 2010, Theunis Potgieter wrote:
>
>> I'm not trying to start a flame war or who is to blame but are there
>> ways I can inspect to see which plugin is causing it, if is a plugin
>> to blame.
>
> You could check those time consuming
On Wed, 20 Oct 2010, Theunis Potgieter wrote:
I'm not trying to start a flame war or who is to blame but are there
ways I can inspect to see which plugin is causing it, if is a plugin
to blame.
You could check those time consuming VDR thread(s) via the "htop"
command and then look for the cor
Am Mittwoch, den 20.10.2010, 11:44 +0200 schrieb Theunis Potgieter:
> Hi mailing list, perhaps this question was asked on other forums
> before (maybe even in a different language). Google failed to bring up
> search results for vdr idle cpu usage. I have vdr 1.7.14 running with
> the only plugins
Hi mailing list, perhaps this question was asked on other forums
before (maybe even in a different language). Google failed to bring up
search results for vdr idle cpu usage. I have vdr 1.7.14 running with
the only plugins dummydevice and streamdev-server, no client is
currently connected and on my