Here are some scripts I find useful in our environment.
- grepXXlog - perform a grep on the same log file name across multiple servers shares looking for a text string. We have multiple servers, each running the same process or set of processes. If there is a problem, we have to find out which server processed that item and look in that particular log file to see what happened. The default log file name is for the current date, but the script has parameters for -# (# of days old) and -note (open the log file in notepad if the text is found). The XX in the script name is for the specific process/share where the files are.
- stripcr - modify a text file in place to replace whatever combination of \r \n with the \n for the current platform. This makes a great 'send to' shortcut on Windows.
- binwords - open a binary file and look for combinations of ascii characters of a minimum specified length and output those strings. This is handy for seeing what calls an executable may be making.
-
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.
|
