Reply from I_am_the_dragon on Jun 24 at 9:26 AM It's not really the software, it's a matter of the size of the file in most cases. If I am looking at a file on a Windows PC I use PFE; But, if I am lucky, I am looking at the file on a Unix server, in which case I can use vi; but, an added bonus of Unix servers is you can parse the file into smaller chunks using head or tail.
And, in most cases, using "all the flags" is over kill, and you end up with a lot of crap you don't need.
I also believe, from my days as a developer, that there used to be a tool that would take a trace file and massage it into something usable.
Additionally, a trick to avoid super huge files full of crap you don't care about is to either 1) not turn on tracing until the user gets to right before what they want to trace or 2) turn on tracing, but, right before they get to where they want to trace, delete the file that has been created so far. Either of these allow you to get rid of a significant part of empty trace information.
peace,
clark 'the dragon' willis
| | | ---------------Original Message---------------
From: Bayarea_Professional
Sent: Sunday, June 24, 2012 1:42 AM
Subject: Trace file too large: Software needed
What software do you guys use to go through large trace files, logs. Most of the computers around here keep hanging when we have all the flags in trace enabled.
Due to this, running the trace with limited flags.
Thanks in advance. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
No comments:
Post a Comment