ndt-users list created

["Kidwell, Michael Mr NISO/APPTIS" <>]

Classification:  UNCLASSIFIED 
Caveats: NONE

There is a utility called "analyze" that is included in the distribution.
The way I use it (and I'm sure that others may have a more efficient method)
is to search the log for the transaction of interest, cut and paste it into
a blank document and save it. Caveat, the paste mechanism may take a single
line of data and make it multiple lines; you'll have to use an editor to get
this corrected. Then you can call "analyze -l <the file_name of your log
snippet>." The option to analyze is "el". If you get a segment fault, review
the caveat. Hope this helps. -- Mike 

-----Original Message-----
From: Clarke Morledge 
[mailto:]
 
Sent: Wednesday, November 01, 2006 3:40 PM
To: 

Subject: Parsing web100srv.log in sync with client output?

Aside from actually peering into the source code, is there a document
available that can help me to parse through the output found in the
web100srv.log?

I am assuming that the web100srv.log file keeps a copy of each of the test
results and so I'd like to be able to correlate that to the client output
from the "Report Problem" button, but I'm having some trouble trying to sync
everything up.

Thanks.

Clarke Morledge
College of William and Mary
Information Technology - Network Engineering Jones Hall (Room 18)
Williamsburg VA 23187
Classification:  UNCLASSIFIED 
Caveats: NONE