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. Presumably, the PC was rebooted in the middle of the send. The user will be calling our support desk to report that her POP session is locked. Should I be running a cron command to kill old pop3d processes? I had hoped that the daemon would look after this case. > Date: Sun, 14 Apr 2002 11:17:23 -0500 > From: Gary Mills <[EMAIL PROTECTED]> > > I see this problem occasionally, and noticed one today: > > UID PID PPID C STIME 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 A V o 1 F 8 F D o M t".., 4096) (sleeping...) > > imapd.conf does not specify `poptimeout', so it should be the default > of ten minutes. Why didn't it time out? -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
