comment on

Not bad! For what it does; it is fine.

What a glowing recommendation. Take something that I worked hard on, thought was good, use a lot, and knock it down. Thanks for your input.

The reason I use an input file for my 500+ servers is that I can update my server list for the 30+ scripts that I run against them in one place.

Sorry, you caught me on a bad day, and I'm a little insulted (although I'm not sure if I should be).

I would probably feel better if you had made code corrections and said, "See, stupid? Like this." rather than just knocking down the code with offhand remarks. But that's the way it goes I suppose...

-OzzyOsbourne

In reply to Re: Re: McAfee Dat Check by OzzyOsbourne
in thread McAfee Dat Check by OzzyOsbourne

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks