tpop3d-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [tpop3d-discuss] tpop3d 1.5.1pre2 (with TLS support)


From: Angel Marin
Subject: RE: [tpop3d-discuss] tpop3d 1.5.1pre2 (with TLS support)
Date: Thu, 14 Nov 2002 20:19:21 +0100

> -----Mensaje original-----
>
> On Thu, Nov 14, 2002 at 07:29:08PM +0100, Angel Marin wrote:
> > Much more funny:
> >
> >  [...]
> > Nov 14 18:25:01 falcone tpop3d[1173]: maildir_new: scanned maildir
> > /var/spool/domains/foo/user (640 messages) in 0.028s
> > Nov 14 18:25:02 falcone tpop3d[1173]: ioabs_tcp_immediate_write: client
> > address@hidden(x.x.x.x): write: Connection reset by peer; closing
> connection
> > Nov 14 18:25:02 falcone tpop3d[1173]: ioabs_tcp_immediate_write: client
> > address@hidden(x.x.x.x): write: Bad file descriptor; closing connection
> > Nov 14 18:25:02 falcone last message repeated 524 times
> >  [...]
> >
> > This error is in the logs since tuesday but I did not see it (argg). I
> > switched back again to 1.4.2.
>
> -- this doesn't actually indicate a new bug, just that
> I've been lazy about logging messages. (What's going on is
> that the client is requesting some response which requires
> about 524 write calls to send; each of these generated and
> logged a `bad file descriptor error' since the first one
> failed and caused the connection to be closed.) I've now
> fixed this in CVS.
>

I know this is not a new bug but the log is much more funny :)

What is new is the situation, after scanning mailbox instead of while
downloading a message. The number of times seems to be near in all cases to
the number of messages stored so may be caused by a reset after the client
sends the UIDL command :? What surprised me was that I did not notice those
errors and only saw those that happened while getting a message.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]