A better solution might be to look at the IO::Interface module as I have suggested here - The reason for this is the dependency on the external binary which your code introduces. This dependency could easily render your code unworkable if the output structure from ifconfig is modified significantly - Also too, as you have not specified a full path to the binary, it would be quite easy for someone with malicious intent to change the path environment and introduce their own ifconfig which could generate some very unexpected and most unwanted results within your code.

I have rambled on this topic previously here.

 

perl -e 's&&rob@cowsnet.com.au&&&split/[@.]/&&s&.com.&_&&&print'

---

---

• 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.