Hello all, hello Duncan, and thx for your response.
For sure, I do have echo commands inside my bash script, mainly because it
is still in debug stage.
Concerning the passed arguments, I know I give 3 args from inside freevo, so
making an "echo $1 $2 $3" inside my script is enough.
My problem is that I don't see any echo inside record.sh.stdout.log.
Despite the 2 log files are well created, the commands inside my
record.shseems not to being executed.
==> Is it possible that there is a problem/bug between the moment when
freevo creates the 2 log files and the moment when it executes the VCR_CMD
command? <==
BTW could you explain me the way python handle the code modification with
respect to its execution cache? I had modified my local_conf.my, and every
time I restarted freevo, it did not took my modif into account. I had been
forced to reboot my linux for these mods to be taken into account. Is there
a command to force the rebuild of that supposed freevo execution cache?
Pirlouwi.
2007/10/8, Duncan Webb <[EMAIL PROTECTED]>:
>
> > Hi,
> > I want to record the mp2 stream coming from an analog channel on my
> > HVR-1300
> > board.
> > The faster method for me to get an immediate result is to configure the
> > VCR_CMD variable, and to load the generic tv recording plugin.
> >
> > For that, I wrote a script : record.sh taking three arguments: the
> channel
> > (ex: E5), the duration in seconds and the name of the file.
> > Used alone, the record.sh script works, producing an mpg file.
> >
> > But used from within freevo, it doesn't work.
> > Freevo (1.7.3) is looking like it is recording, and two log files named
> "
> > record.sh.stderr.log" and "record.sh.stdout.log" are created but remains
> > empty.
>
> Depends if you have any echo commands in your script, it not then they
> will be empty.
>
> > How could I debug this problem?
>
> Easiest way is to see what arguments are being passed into the script,
> some thing like:
> echo $*
> echo "$@"
> at the top of the script will print the arguments.
>
> Then it should be easy.
>
> You can also use as the first line:
> #!/bin/bash -x
> or
> #!/bin/bash -v
> Which will print out the command that are being executed and the script,
> respectively.
>
> Duncan
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users
