Andre Bischof wrote:
Klaus Schmidinger wrote: ...
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".
root@linux:/downloads/vdr/1.3.38/vdr-1.3.38# ps -T u -C vdr USER PID SPID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND vdr 9709 9709 0.7 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9710 48.2 1.2 34268 11624 ? Rsl 18:34 0:13 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9711 48.2 1.2 34268 11624 ? Rsl 18:34 0:13 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9713 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9714 0.0 1.2 34268 11624 ? SNsl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9715 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9716 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9717 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p
so they are two!
Jan 15 18:34:03 linux vdr[9709]: VDR version 1.3.38 started Jan 15 18:34:03 linux vdr[9709]: switched to user 'vdr' Jan 15 18:34:03 linux vdr[9709]: running as daemon (tid=9709) Jan 15 18:34:03 linux vdr[9709]: loading plugin: ./PLUGINS/lib/libvdr-remote.so.1.3.38 Jan 15 18:34:03 linux vdr[9709]: loading plugin: ./PLUGINS/lib/libvdr-dxr3.so.1.3.38 Jan 15 18:34:03 linux vdr[9709]: loading ./sources.conf Jan 15 18:34:03 linux vdr[9709]: loading ./diseqc.conf Jan 15 18:34:03 linux vdr[9709]: loading ./channels.conf Jan 15 18:34:03 linux vdr[9709]: loading ./svdrphosts.conf Jan 15 18:34:03 linux vdr[9709]: loading ./keymacros.conf Jan 15 18:34:03 linux vdr[9709]: reading EPG data from /video/epg.data
searched tids --- Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9710) Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9711) --- searched tids
Jan 15 18:34:03 linux vdr[9709]: probing /dev/dvb/adapter0/frontend0 Jan 15 18:34:04 linux vdr[9709]: found 1 video device Jan 15 18:34:04 linux vdr[9709]: initializing plugin: remote (0.3.4): Remote control Jan 15 18:34:04 linux vdr[9709]: initializing plugin: dxr3 (0.2.5): Hardware MPEG decoder Jan 15 18:34:04 linux vdr[9709]: tuner on device 1 thread started (pid=9709, tid=9713) Jan 15 18:34:04 linux vdr[9709]: section handler thread started (pid=9709, tid=9714) Jan 15 18:34:05 linux vdr[9709]: dxr3: configure: video mode: PAL Jan 15 18:34:05 linux vdr[9709]: dxr3: configure: audio mode: analog Jan 15 18:34:05 linux vdr[9709]: dxr3: intf: brightness=500,contrast=500,saturation=500 at init Jan 15 18:34:05 linux vdr[9709]: setting primary device to 1 Jan 15 18:34:05 linux vdr[9709]: device 1 has no MPEG decoder Jan 15 18:34:05 linux vdr[9709]: trying device number 2 instead Jan 15 18:34:05 linux vdr[9709]: setting primary device to 2 Jan 15 18:34:05 linux vdr[9709]: SVDRP listening on port 2001 Jan 15 18:34:05 linux vdr[9709]: loading ./themes/sttng-default.theme Jan 15 18:34:05 linux vdr[9709]: starting plugin: remote Jan 15 18:34:05 linux vdr[9709]: device /dev/input/event4: Budget-CI dvb ir receiver saa7146 (0) Jan 15 18:34:05 linux vdr[9709]: remote: using '/dev/input/event4' Jan 15 18:34:05 linux vdr[9709]: remote-event4: exclusive access granted Jan 15 18:34:05 linux vdr[9709]: starting plugin: dxr3 Jan 15 18:34:05 linux vdr[9709]: loading ./themes/sttng-default.theme Jan 15 18:34:05 linux vdr[9709]: remote control remote-event4 - learning keys Jan 15 18:34:05 linux vdr[9709]: dxr3: cSPUEncoder::Flush: OSD data size: 8741 Jan 15 18:34:05 linux vdr[9709]: device /dev/input/event4: Budget-CI dvb ir receiver saa7146 (0) Jan 15 18:34:05 linux vdr[9709]: DXR3 video output thread started (pid=9709, tid=9716) Jan 15 18:34:05 linux vdr[9709]: DXR3 audio output thread started (pid=9709, tid=9715) Jan 15 18:34:08 linux vdr[9709]: dxr3: cSPUEncoder::Flush: OSD data size: 8546
Now that they are identified, what should I do next?
I can't see s.th. wrong with /video: root@linux:/# la /video/ total 20287988 drwxrwxr-x 17 vdr users 4096 Jan 15 17:21 . drwxr-xr-x 27 root root 4096 Jan 14 15:19 .. drwxr-xr-x 3 vdr users 4096 Dec 9 20:18 Der_200-Jahre-Mann
What's inside "Der_200-Jahre-Mann"? Any non-VDR subdirectories?
/video belongs vdr, as do _old_ recordings. The menue for recordings does not show my old recordings.
Where are those _old_ recordings?
BTW for the moment I start vdr from within my compile-dir vdr-1.3.38 with: root@linux:/downloads/vdr/1.3.38/vdr-1.3.38# ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3.6 -p 2001 --video=/video -w 60-u vdr -g vdr -P remote -P dxr3
There's a blank mitting between 60 and -u. Also, the GRAB directory (option -g) must be a full path name.
thus the video-dir should be right?
Do you have any guesses what my problem could be? What does the "video directory scanner thread" do?
Well, it scans the video directory ;-)
Are you sure that there is no other data in your video directory that might cause VDR to do unnecessary work?
Klaus