comment on

I have the same problem with perl 5.10.1 under linux, but not with the original code, that works:

CMD        : >>echddo 'arghh'<<
RETURN_CODE: >>32512<<
CMD_RESULT : >>sh: echddo: command not found
<<
[download]

However, I want to trap an error from a simple command, but a bad one. For example, a misspelled command:

my $cmd = "hostnam";

Here I can't trap the error:

CMD        : >>hostnam<<
RETURN_CODE: >>-1<<
CMD_RESULT : >><<
[download]

The odd thing is that if I redirect STDOUT/STDERR to a file instead, the error is redirected as expected.

`$cmd 1>./tmp 2>&1`;
my $cmd_rc = $?;
my $cmd_result = `cat ./t`;
[download]

CMD        : >>hostnam<<
RETURN_CODE: >>32512<<
CMD_RESULT : >>sh: hostnam: command not found
<<
[download]

Is there a better way to get the expected behavior without resorting to a file?

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks