Having removed the extra "`" I end up with the following errors:

sh: -c: line 1: syntax error near unexpected token `;' sh: -c: line 1: `;/somepath/foo'

"Lesser problems include lack of error checking, lack of proper conversion from strings to shell literals, and possibly useless use of backticks."

By error checking do you mean that I should be using print, for example, after the script cd's into each directory as a check to see if the script is indeed cd'ing into each directory?

Could you elaborate on the latter two? Where is the script converting from strings to shell literals and what should I do to remedy it? Are the backticks simply unnecessary or do they need to be replaced by system or exec? Like I said, I'm new to this and I'm learning by trial and error.


In reply to Re: problem running executable in subdirectories by apollo
in thread problem running executable in subdirectories by apollo

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.