Hi!
When executing a system op using the backtick method, the standard
output is caught and returned in the assigned variable:
output= `ls -Al`
I am wondering what happens with the standard error output? I have
written a script that executes well in the happy path scenario, but
for the case where the invoked system tool is writting to stderr I
have no idea how to trap that.
Any help and ideas are highly appreciated,
./alex
···
--
.w( the_mindstorm )p.
Since it's a system command, you can ask it to redirect stderr to stdout:
output = `ls -Al 2>&1`
···
On 10/26/06, Alexandru Popescu <the.mindstorm.mailinglist@gmail.com> wrote:
Hi!
When executing a system op using the backtick method, the standard
output is caught and returned in the assigned variable:
output= `ls -Al`
I am wondering what happens with the standard error output? I have
written a script that executes well in the happy path scenario, but
for the case where the invoked system tool is writting to stderr I
have no idea how to trap that.
Any help and ideas are highly appreciated,
Which shell is ruby using?
Can I control which shell ruby is using?
-Dan
···
On 10/26/06, Wilson Bilkovich <wilsonb@gmail.com> wrote:
On 10/26/06, Alexandru Popescu <the.mindstorm.mailinglist@gmail.com> > wrote:
> Hi!
>
> When executing a system op using the backtick method, the standard
> output is caught and returned in the assigned variable:
>
> output= `ls -Al`
>
> I am wondering what happens with the standard error output? I have
> written a script that executes well in the happy path scenario, but
> for the case where the invoked system tool is writting to stderr I
> have no idea how to trap that.
>
> Any help and ideas are highly appreciated,
Since it's a system command, you can ask it to redirect stderr to stdout:
output = `ls -Al 2>&1`
--
bikle@bikle.com