"tcpflags 0x18<PUSH,ACK>; tcp_do_segment" kernel messages

Stefan Lambrev stefan.lambrev at moneybookers.com
Thu Aug 16 00:37:34 PDT 2007


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



More information about the freebsd-current mailing list