You are sure that the ssh config allows you to run the failing commands, aren't you ?

Also, as anony monk has already said, try printing the value of $stderr to get at the error from the ssh session e.g. print $stdout ? $stdout : $stderr;.

You could also try pre-fixing status.sh with $HOME i.e. $HOME/status.sh since . is not normally on the path for an ssh login because of it's inherent insecurity, ensuring that the command is set up within single quotes in order to ensure that it is expanded at the remote end $command = '/usr/bin/sh $HOME/status.sh';.

A user level that continues to overstate my experience :-))

In reply to Re: SSH and Scripting by Bloodnok
in thread SSH and Scripting by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.