The mplayer plugin doesn't work when I start vdr from inittab. It works ok if vdr is started from the console.
I've seen hints that $USER and $HOME need to be set, but setting these in my startup script doesn't change anything.. Anyone got any idea what's missing?
Also, it would be an idea to be able to get the log output from the mplayer plugin somehow.
En/na Torgeir Veimo ha escrit:
The mplayer plugin doesn't work when I start vdr from inittab. It works ok if vdr is started from the console.
Maybe it needs a console to work? I side stepped the problem by running vdr inside a screen session, so it has a console and I can attach to it when I want
I've seen hints that $USER and $HOME need to be set, but setting these in my startup script doesn't change anything.. Anyone got any idea what's missing?
Also, it would be an idea to be able to get the log output from the mplayer plugin somehow.
See above: using screen I can see vdr (and plugins) output.
Bye
Hi,
Torgeir Veimo wrote:
The mplayer plugin doesn't work when I start vdr from inittab. It works ok if vdr is started from the console.
I've seen hints that $USER and $HOME need to be set, but setting these in my startup script doesn't change anything.. Anyone got any idea what's missing?
Also, it would be an idea to be able to get the log output from the mplayer plugin somehow.
This is most likely because the PATH variable is not set. So set the PATH variable in your runvdr script and mplayer will be working fine. At least it is working here in my machine.
André
On 6 Oct 2008, at 19:00, André Weidemann wrote:
Hi,
Torgeir Veimo wrote:
The mplayer plugin doesn't work when I start vdr from inittab. It works ok if vdr is started from the console.
I've seen hints that $USER and $HOME need to be set, but setting these in my startup script doesn't change anything.. Anyone got any idea what's missing?
Also, it would be an idea to be able to get the log output from the mplayer plugin somehow.
This is most likely because the PATH variable is not set. So set the PATH variable in your runvdr script and mplayer will be working fine. At least it is working here in my machine.
I tried now, with a /etc/rc.vdr containing;
#!/bin/sh # # Start VDR
export HOME="/root" export USER="root" export LANG="en_US" export PATH="/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin"
/bin/setserial /dev/ttyS1 uart none; /sbin/modprobe lirc_serial
/usr/bin/screen -dmS vdr /usr/local/bin/runvdr 2>&1 >| /tmp/vdrlog.txt &
Still doesn't work. rc.vdr is started from /etc/rc.local.
Maybe the problem is the extended runvdr script by Udo Richter I'm using?
On 6 Oct 2008, at 23:41, Torgeir Veimo wrote:
/usr/bin/screen -dmS vdr /usr/local/bin/runvdr 2>&1 >| /tmp/ vdrlog.txt &
Sorry for the noise.. Reattaching to the screen instance I instantly realized that the cause was an erroneous video out parameter..
Hi,
Torgeir Veimo wrote:
Sorry for the noise.. Reattaching to the screen instance I instantly realized that the cause was an erroneous video out parameter..
why not using mplayer.sh? It is a shell script that has some additional features.
Bye, Matthias