On Wed, Feb 04, 2004 at 10:18:49AM +0100, Niklas Bergh wrote:
> It is an effect of a connection being closed quite immediately after it
> was opened. Could we move the enqueueing of the identify message a
> little while later?
No. Identify has to be the first message sent. It's logged at NORMAL
be
gt; Sent: den 4 februari 2004 01:04
> To: [EMAIL PROTECTED]
> Subject: Re: [freenet-support] Failed to send
> IdentifyPacketMessage Errors
>
>
> I doubt this is new. I see these with older builds on my
> machine a lot
> as well.
>
> Nikita.
>
> Kevin
I doubt this is new. I see these with older builds on my machine a lot
as well.
Nikita.
Kevin Bennett wrote:
Seeing hundreds of these today, roughly between 1 and 4 per second:
03-Feb-2004 21:39:35 (freenet.IdentifyPacketMessage, YThread-42, NORMAL):
Failed to send IdentifyPacketMessage: freen
