This problem does not occur on an otherwise standard RedHat 7.1
system with an unmodified 2.4.5 kernel from kernel.org, so that should
narrow it down to one of the first two.
Andrew Mann
At 03:12 PM 7/16/2001 -0700, you wrote:
> > If so, then, as per the aforementioned followup, the problem is probably
> > in the Linux kernel's time-stamping code. As such, I'd take this up
> > with Red Hat, as it appears not to be a problem with tcpdump.org's
> > libpcap code;
>
>Note that the current CVS code (which doesn't differ at all in the
>handling of time stamps from the 0.6.2 code) works Just Fine on a Debian
>system here with a 2.4.4 kernel; perhaps there was a bug in the official
>2.4.2 kernel that got fixed by 2.4.4, or perhaps Red Hat have "improved"
>the kernel in a way that breaks high-resolution time stamping (or,
>although I suspect this is less likely, Debian fixed the kernel but the
>fix isn't in the official kernels or the Red Hat kernel).
>
>Again, that says the next step is to complain to Red Hat, or perhaps to
>ask the linux-kernel or linux-net list about the problem.
>-
>This is the TCPDUMP workers list. It is archived at
>http://www.tcpdump.org/lists/workers/index.html
>To unsubscribe use
>mailto:[EMAIL PROTECTED]?body=unsubscribe
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
