nasty brokeness!

[Peter Van Epp]

	I had the thought that it might be that with the file argus is in
control of the fetch (and won't fetch the next one until it is ready for it)
but on the wire it may be getting overrun by a new packet before its finished
with the old one somehow.

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada


> 
> Hey Peter,
> Argus processes time in completely different
> ways when it reads from a packet file vs. when
> it reading off an interface.
> 
> When Argus is running in near real time, the concept
> of ArgusGlobalTime is just system time and there are
> a lot of situations where Argus is idle, not processing
> packets, but busy grooming its internal structures.
> 
> When reading from a file, time is derived from the
> packet headers themselves, rather than from the
> system clock, there is no idle time at all in that
> we are constantly processing packets until EOF.
> 
> With such major differences, its not surprising that
> there may be a problem.  I'm just interested in the
> fact that the problem occurs off the wire, rather
> than out of the file.
> 
> I've already found a few gotchas with the time, now
> that I'm looking into this particular problem, but
> nothing yet that would explain your bug.  I'll see
> what I can do this weekend.
> 
> 
> Carter
> 
> Carter Bullard
> QoSient, LLC
> 300 E. 56th Street, Suite 17A
> New York, New York  10022
> 
> carter at qosient.com
> Phone +1 212 813-9426
> Fax   +1 212 813-9426
>