[Rock-dev] Redirecting STDOUT/STDERR for a deployment

[Chris Mueller]

Thats the solution i needed.

For all other rock users here is the documetation from the sources for this:

32     # call-seq:
33     #   Orocos.run('mod1', 'mod2')
34     #   Orocos.run('mod1', 'mod2', :wait => false, :output => 
'%m-%p.log')
35     #   Orocos.run('mod1', 'mod2', :wait => false, :output => 
'%m-%p.log') do |mod1, mod2|
36     #   end
37     #
38     # Valid options are:
39     # wait::
40     #   wait that number of seconds (can be floating-point) for the
41     #   processes to be ready. If it did not start into the provided
42     #   timeout, an Orocos::NotFound exception raised.
43     # output::
44     #   redirect the process output to the given file. The %m and %p
45     #   patterns will be replaced by respectively the name and the PID of
46     #   each process.

On 18.07.2012 15:46, Jakob Schwendner wrote:
> hi chris,
>
> On 07/18/2012 03:18 PM, Chris Mueller wrote:
>> Hi,
>>
>> does anyone know how i can redirect STDOUT and STDERR for a running
>> deployment/task into e.g. a file via the orocos.rb interface?
>>
>> Orocos.run "deployment" do |proc|
>>       task = TaskContext.get "task"
>> end
> you could try to use Orocos.run "deployment", :output => file do |proc|
> This is an option on the Bundles interface. Not sure if it is also in
> the orocos interface. And I am also not sure what file should be.
>
> cheers,
>
> Jakob
>
> _______________________________________________
> Rock-dev mailing list
> Rock-dev at dfki.de
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev