Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
First I want to thank everybody for the comments.

We know for certain that it is picking up the .cshrc settings because when we remove the PATH statements all of the alternate commands are working properly, and hence my assumption that they are using csh when backticking commands in perl. Unfortunately some of the people here running the perl scripts need to have both special PATH and ENVIRONMENT settings for the perl tools as well as other tools, and they both conflict with each other. It is very much a chicken and egg problem.

Since we are getting both sets of tools from a corporate source repository, and we really are not at liberty to make changes to them that is why I was just hoping for a quick one change of code to change the backtick behavior that I could send of to HQ and hope that it would get implemented some day. Even though using the IPC modules is a good alternative, I doubt I'll be able to get somebody to change the implementation under the hood of these scripts.

Again, thank you all for posting. Even though I cannot do much in this case I will definitely check out IPC::Open3 and IPC::Run at least for my own scripts. Given how touch and go the environment is here I don't want to be adding to this very huge mess.

In reply to Re: Specifying a shell for use with Backticks by gaspodethewonderdog
in thread Specifying a shell for use with Backticks by gaspodethewonderdog

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

  • 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 or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (3)
As of 2021-05-17 00:19 GMT
Find Nodes?
    Voting Booth?
    Perl 7 will be out ...

    Results (152 votes). Check out past polls.