Yep, I showed him how to print a variable to get it's value, and I showed him -c and -d. Thing is, I only gave him the overview. Assuming there's a second lecture (sermon? Nahhh, let's not pursue the Monk metaphor), I'll need to pick one thing and go into it in more depth. At this point, I'm leaning towards helping him write a simple script to parse netstat into name=value pairs and either writing the data to a logfile, mailing it somewhere, or posting it to a web page.
One thing I addressed, independent of perl syntax, was that tools should have similar interfaces, reporting mechanisms and output formats. That way, an eventual toolsuite can grow without having to reinvent the wheel, and the code is more maintainable.
-Logan
"What do I want? I'm an American. I want more."
-
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.
|
