Date: Thu, 16 Aug 2007 10:37:32 +0300 From: Stefan Lambrev <stefan.lambrev@moneybookers.com> To: Eygene Ryabinkin <rea-fbsd@codelabs.ru> Cc: current@freebsd.org Subject: Re: "tcpflags 0x18<PUSH,ACK>; tcp_do_segment" kernel messages Message-ID: <46C3FEBC.80409@moneybookers.com> In-Reply-To: <20070815172731.GR988@void.codelabs.ru> References: <20070806224112.GA21876@muon.bluestop.org> <20070807073920.GV50228@void.codelabs.ru> <46C18B60.8050400@moneybookers.com> <20070814145759.GB25169@void.codelabs.ru> <20070814193150.GA21553@rot26.obsecurity.org> <46C30FA6.7060108@moneybookers.com> <20070815145640.GQ988@void.codelabs.ru> <46C319DD.3010806@moneybookers.com> <20070815172731.GR988@void.codelabs.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Eygene Ryabinkin wrote: > The previous one: client mb7.intra.net had thrown his 'QUIT' and > closed the socket, thus he is not interested in the server's response. > Judging by the normal end of the task that you're citing below, the > normal client workflow is to wait for the server's response to the > 'quit' message and to close the socket only after it. So something > unusual happening to the client and it is really interesting to > look at the client's sources to see what's up. > > To clarify a bit: are all two servers running -CURRENT, or just the > client one? > > Thank you! > Only mb7 is -current (i386), mb4 is 6.2 (i386). The server is postfix, but the client is binary and we do not have the sources. I'll see what the creators can tell about this. -- Best Wishes, Stefan Lambrev ICQ# 24134177
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46C3FEBC.80409>