The printf() is only in HEAD for feedback purposes. I'd like to leave
it in there just a little while longer (maybe a week at the rate things
are going). It looks like more people are hitting this bug(fix) then
we previously thought would hit it, which is actually somewhat worrying
because it only occurs when you get out-of-order timestamp replies.
Could you tell me what services were running or what you were doing
when you got the warnings? Are you running a web server? Talking
to windows boxes at all?
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:>=20
:> Which appears to just be triggered by a mechanism to drop
:> bad packets. Is this correct? Is this something I should be
:> concerned about?
:>=20
:Matt,
:
:I'm seeing these too. Can you please remove the relevant
:printf() or at least limit it to the ``if (verbose)'' or
:DIAGNOSTIC, whatever is more appropriate?
:
:
:Cheers,
:--=20
:Ruslan Ermilov Sysadmin and DBA,
:[EMAIL PROTECTED] Sunbay Software AG,
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
