I believe on certain systems there's a race condition (well, race is a
wrong word, more like a kernel feature ;) between select and accept:
It is possible that select() will return filehandle as readable, but an
accept on it will fail with 'socket not connected'.
There's been much discussion on linux/bsd lists as far as what's correct
implementation of such situation (RST from client received between select
and accept), but in general, this is totally harmless. Your client
disconnected before its request could be accepted.
-alex
On Wed, 25 Jul 2001, Lawrence Greenfield wrote:
> man accept and post what the error means.
>
> Larry
>
> Date: Wed, 25 Jul 2001 20:44:04 +0200
> From: Ingo Herz <[EMAIL PROTECTED]>
>
> Hello,
> I'm running cyrus-imap 2.0.15 on an IBM F50 (AIX 4.3.3) for about a week
> now. Had to do very little changes in the source, but that's not the problem:
> our logs are filled with the following messages (~every 10 min):
>
> pop3d[43562]: accept failed: Socket is not connected
>
> As this warnings are generated in service.c and service-thread.c and there
> are a lot of lookalike defines in the switch perhaps I can simply add this
> ("ENOTCONN") to it or is this (another) "feature" of AIX?
>
> Any hints are welcome!
>
> regards,
> Ingo
>
>
>
