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 which implement a SOCK_STREAM > ensure that data is not lost or duplicated. If a piece of data > for which the peer protocol has buffer space cannot be > successfully transmitted within a reasonable length of time, > then the connection is considered to be dead. When > SO_KEEPALIVE is enabled on the socket the protocol checks in a > protocol-specific manner if the other end is still alive. A > SIGPIPE signal is raised if a process sends or receives on a > broken stream; this causes naive processes, which do not handle > the signal, to exit. SOCK_SEQPACKET sockets employ the > > I guess I'd like to know if any data is trying to be transmitted to > the client (use "tcpdump host <clientname>" on the server for a couple > of hours?).
Yes, there is traffic every few seconds with `snoop': electra.cc.umanitoba.ca -> net41.anthro.umanitoba.ca TCP D=2034 S=110 Ack=1055534117 Seq=3063126801 Len=1 Win=24656 net41.anthro.umanitoba.ca -> electra.cc.umanitoba.ca TCP D=110 S=2034 Ack=3063126801 Seq=1055534117 Len=0 Win=0 My guess is that the mail reader on the client disappeared. > I don't consider 12 days a reasonable amount of time to have to wait. -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
