Project

General

Profile

Actions

Bug #606

closed

no GetTSTimeoutHandler configured

Added by Anonymous about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
03/16/2011
Due date:
% Done:

100%

Estimated time:

Description

Plugin is started with --GetTSTimeoutHandler=/usr/bin/dynamite-reload (-Pdynamite --GetTSTimeoutHandler=/usr/bin/dynamite-reload)

On reload, this happens:

Mar 16 21:12:37 vdr vdr: [2240] dynamite: no GetTSTimeoutHandler configured, arg: pci:v000013D0d00002103sv000013D0sd00002103bc02sc80i00

The udev rule works, the device is detached

root@vdr:~# svdrpsend plug dynamite lstd
220  SVDRP svdrpd 0.0.1; Wed Mar 16 21:20:37 +0100 2011
900 1 /dev/dvb/adapter0/frontend0
221  closing connection (quit)

Actions #1

Updated by steffen_b about 13 years ago

Just to add more facts

Two DVB devices. One is configured for TSTimeout, dynamite has configured the --GetTSTimeoutHandler
- The watchdog at the device happens
- the script should be called, but above log happens
- the script is configured and available
- the script is not executed

It could be that the script has triggered that, but then the message would be misleading. I still verify that.

Actions #2

Updated by lhanisch about 13 years ago

  • Assignee set to lhanisch
Actions #3

Updated by lhanisch about 13 years ago

Do you see something like "dynamite: installing GetTSTimeoutHandler /usr/bin/dynamite-reload" in the log?

Or do you have an empty "dynamite.GetTSTimeoutHandler =" in your setup.conf? That would delete the handler passed on the commandline...

Ah, read the README... :-)

-P "dynamite --GetTSTimeoutHandler /path/to/program"

no equal-sign... :-)

Actions #4

Updated by steffen_b about 13 years ago

Ah , now i can see that log entry too. Sry

To excuse myself:

 -a CMD,   --audio=CMD    send Dolby Digital audio to stdin of command CMD
 -c DIR,   --config=DIR   read config files from DIR (default: /var/lib/vdr)

short argument -> space, long argument -> =
Maybe it should be:
-t CMD --tstimeout=CMD set program CMD to be called on TS-timeout

Actions #5

Updated by lhanisch about 13 years ago

  • % Done changed from 0 to 90

Only if I would use "getopt"... :-)

I will think about it.

Actions #6

Updated by lhanisch about 13 years ago

  • Status changed from New to Closed
  • Target version set to 0.0.x
  • % Done changed from 90 to 100

with dynamite 0.0.5m it will use "getopt_long", please take a look at the README.

Commandline Arguments
---------------------
-u, --log-udev
        log all udev events to syslog (useful for diagnostics)
-d, --dummy-probe
        start dummy-device probe (useful for experiments)
-t, --GetTSTimeout=n
        set default GetTS-timeout to n seconds
-h, --GetTSTimeoutHandler=/path/to/program
        set program to be called on GetTS-timeout
Actions

Also available in: Atom PDF