Andre Bischof wrote: > ... > I couldn't really track down this error, but I installed almost > everything new, thus now running vdr 1.3.38 with only dxr3 and remote > plugins. I have it working, with video/audio, but vdr keeps eating alot > ressources, more than it took before, see top: > > top - 16:01:32 up 22:55, 8 users, load average: 2.86, 2.43, 1.48 > Tasks: 192 total, 2 running, 189 sleeping, 0 stopped, 1 zombie > Cpu(s): 4.8% us, 58.7% sy, 0.1% ni, 0.0% id, 35.8% wa, 0.1% hi, > ^^^^^^^^^^^^^^^^^ > 0.5% si > Mem: 906588k total, 897272k used, 9316k free, 191060k buffers > Swap: 2088440k total, 124k used, 2088316k free, 97000k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 6943 vdr 16 0 45020 16m 2760 S 60.9 1.9 6:57.85 vdr > > > There's harddisk activity all the time when I start vdr, could it be > that this comes from reading my video dir (about 80GB, there is s.th. in > the logs saying: > > Jan 15 15:50:24 linux vdr[6943]: loading ./keymacros.conf > Jan 15 15:50:24 linux vdr[6943]: video directory scanner thread started > (pid=6943, tid=6944) > Jan 15 15:50:24 linux vdr[6943]: video directory scanner thread started > (pid=6943, tid=6945) > Jan 15 15:50:24 linux vdr[6943]: reading EPG data from /video/epg.data > > I really would like to know what vdr (6943, see top) is doing exactly, > but I don't know how - anyone who could give me a hint? If you'd like > more information, please let me know. You could start by consulting the log file to find out which thread actually eats up the most CPU time. You can use ps -T u -C vdr to find out the thread's SPID and locate the corresponding "thread ... started" line in the log where it says "tid=nnn". Klaus
