Re: idle pop3d never times out

2002-04-22 Thread Ilya
Have you found any solution, work around ? I am having the same problem, with both imapd and pop3d as you see they hang there since wednesday. the clients are outlook express. 42564 0.0 0.2 2392 316 p2- IWed12AM 0:02.67 /usr/local/cyrus2/bin/master cyrus42821 0.0 0.4 3752

Re: idle pop3d never times out

2002-04-22 Thread Gary Mills
On Mon, Apr 22, 2002 at 03:44:49PM -0400, Ilya wrote: Have you found any solution, work around ? I am having the same problem, with both imapd and pop3d It's okay for imapd to hang around, because the client can reuse the connection indefinitely. This is normal. IMAP clients can also make

Re: idle pop3d never times out

2002-04-16 Thread Gary Mills
On Mon, Apr 15, 2002 at 02:40:20PM -0400, Lawrence Greenfield wrote: Date: Sun, 14 Apr 2002 18:35:18 -0500 From: Gary Mills [EMAIL PROTECTED] electra.cc.umanitoba.ca - net41.anthro.umanitoba.ca TCP D=2034 S=110 Ack=1055534117 Seq=3063126801 Len=1 Win=24656

Re: idle pop3d never times out

2002-04-15 Thread Gary Mills
On Mon, Apr 15, 2002 at 02:55:10PM -0400, Igor Brezac wrote: On Mon, 15 Apr 2002, Lawrence Greenfield wrote: It appears that the client is still there (you have an active TCP session) but I don't know if it's making progress. Are the sequence numbers changing? It's almost as if

RE: idle pop3d never times out

2002-04-15 Thread Mike Brady
Of Gary Mills Sent: Tuesday, 16 April 2002 10:05 a.m. To: Lawrence Greenfield Cc: [EMAIL PROTECTED] Subject: Re: idle pop3d never times out On Mon, Apr 15, 2002 at 02:40:20PM -0400, Lawrence Greenfield wrote: It appears that the client is still there (you have an active TCP session

Re: idle pop3d never times out

2002-04-15 Thread Gary Mills
On Tue, Apr 16, 2002 at 11:33:00AM +1200, Mike Brady wrote: This sounds very similar to a problem that I reported a couple of weeks ago with imapd not closing the socket in 2.1.3. Maybe there is something not quite right with the socket handling in 2.x in general. No, it's not the same. In

idle pop3d never times out

2002-04-14 Thread Gary Mills
I see this problem occasionally, and noticed one today: UID PID PPID CSTIME TTY TIME CMD cyrus 6247 725 0 Apr 02 ?0:01 pop3d `lsof' shows that file descriptors 0, 1, and 2 have an established TCP connection to a client workstation. `truss' shows: write(1, A

Re: idle pop3d never times out

2002-04-14 Thread Ken Murchison
Gary Mills wrote: I see this problem occasionally, and noticed one today: UID PID PPID CSTIME TTY TIME CMD cyrus 6247 725 0 Apr 02 ?0:01 pop3d `lsof' shows that file descriptors 0, 1, and 2 have an established TCP connection to a client workstation.

Re: idle pop3d never times out

2002-04-14 Thread Gary Mills
On Sun, Apr 14, 2002 at 01:50:31PM -0400, Ken Murchison wrote: Gary Mills wrote: I see this problem occasionally, and noticed one today: UID PID PPID CSTIME TTY TIME CMD cyrus 6247 725 0 Apr 02 ?0:01 pop3d `lsof' shows that file descriptors

Re: idle pop3d never times out

2002-04-14 Thread Lawrence Greenfield
the Cyrus software will never interrupt a TCP send to obey the timeouts; this guy isn't responding and a TCP send could take up to a couple of hours to time out I think. Larry Date: Sun, 14 Apr 2002 11:17:23 -0500 From: Gary Mills [EMAIL PROTECTED] I see this problem occasionally, and

Re: idle pop3d never times out

2002-04-14 Thread Gary Mills
On Sun, Apr 14, 2002 at 04:54:35PM -0400, Lawrence Greenfield wrote: the Cyrus software will never interrupt a TCP send to obey the timeouts; this guy isn't responding and a TCP send could take up to a couple of hours to time out I think. After 12 days, I'd say it's not going to time out.

Re: idle pop3d never times out

2002-04-14 Thread Gary Mills
On Sun, Apr 14, 2002 at 06:49:44PM -0400, Lawrence Greenfield wrote: Hmm. So there's clearly some sort of problem in the socket implementation then. If the packet can't be delivered successfully, the write() system call is suppose to return EPIPE: The communications protocols