[nos-bbs] trace files
George [ham] VerDuin
k8rra at ameritech.net
Wed Sep 22 15:33:28 EDT 2010
Interesting Michael...
Michael Fox - N6MEF wrote:
>
>
> Also, when I specify a filename, the file is created, but has zero
> size and nothing in it until I exit JNOS. Really BAD. So now I have
> no trace output at all while JNOS is operating and, if it crashes, it
> may not be able to write the trace output file.
>
Almost accurate.
Linux buffers output so while there is zero on HD there is non-zero in
buffer waiting to fill up to the write threshold size.
Try a no-file trace command on the selected interface to cause JNOS to
purge the buffer before changing the output path to the F9 tty. There
are more elegant solutions.
>
>
> So, putting this together, tracking down a problem is virtually
> impossible.
>
Well -- it certainly changes the timeliness and approach to trouble
shooting.
>
>
> It seems to me that:
>
> 1) JNOS should always write to the F9 session (unless strace is off,
> in which case, it would write to the F10 session)
>
> 2) If a file is names, then JNOS would ALSO write to the file
>
> 3) JNOS should write to the file as it is running. NOT buffer
> everything up until it terminates.
>
>
>
> Is anyone else having this problem? Is there a workaround?
>
Admittedly some issues solve best with immediate view of detail
traffic. For most of the issues I have maybe a year(+) of trace on the
RF ports because I have the space to waste(?). I have seen the thing
you call out, but not found it any disadvantage. Maybe even an
advantage -- I typically filter the trace to aid in focus on only what
I'm looking for. Sometimes I edit the trace to add personal comments.
Comments help me focus on the issue -- especially when setting the issue
aside for a while then picking it up again later doesn't require me to
re-discover fact from the previous review.
The way I work is not for everybody [for certain].
>
>
>
> Michael
>
> N6MEF
>
Good luck with your JNOS
Skip
More information about the nos-bbs
mailing list