[vdr] caught signal 2

[hm@seneca.muc.de]

Hi,

for a couple of days now I've got a strange problem with vdr-1.3.16.
Soon after starting my VDR up, vdr will report "caught signal 2" to syslog
and die, like so: 

Dec 12 20:35:39 linvdr vdr[3498]: setting watchdog timer to 60 seconds
Dec 12 20:35:39 linvdr vdr[3498]: retuning due to modification of channel 2
Dec 12 20:35:39 linvdr vdr[3498]: switching to channel 2
Dec 12 20:35:39 linvdr vdr[3506]: transfer thread started (pid=3506, tid=81926)
Dec 12 20:35:39 linvdr vdr[3507]: receiver on device 1 thread started (pid=3507, tid=98311)
Dec 12 20:35:39 linvdr vdr[3508]: TS buffer on device 1 thread started (pid=3508 , tid=114696)
Dec 12 20:35:40 linvdr vdr[3498]: caught signal 2
Dec 12 20:35:40 linvdr vdr[3506]: transfer thread ended (pid=3506, tid=81926)
Dec 12 20:35:41 linvdr vdr[3508]: TS buffer on device 1 thread ended (pid=3508, tid=114696)
Dec 12 20:35:41 linvdr vdr[3507]: buffer stats: 70312 (3%) used
Dec 12 20:35:41 linvdr vdr[3507]: receiver on device 1 thread ended (pid=3507, tid=98311)
Dec 12 20:35:41 linvdr vdr[3498]: buffer stats: 182736 (8%) used
Dec 12 20:35:41 linvdr vdr[3504]: KBD remote control thread ended (pid=3504, tid =65541)

Strange thing is, the machine was working all day long yesterday, and this
happened only in the evening. I had to restart the box because it wouldn't
react to the remote any more (using the remote module with the av7110 IR). 

It is always the master thread that reports signal 2. All other threads
keep running, strangely. And after a warm restart, "./av7110_loadkeys
/video/my.rc5" will hang and not continue. It needs a reboot... 

Any idea who or what sends a SIGINT to vdr in the first place? 

-- 
The only problem with being a man of leisure is that you can never stop
and take a rest.