From owner-freebsd-current Wed Nov 25 00:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11034 for freebsd-current-outgoing; Wed, 25 Nov 1998 00:44:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11029 for ; Wed, 25 Nov 1998 00:44:47 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id DAA27850; Wed, 25 Nov 1998 03:44:33 -0500 (EST) Date: Wed, 25 Nov 1998 03:44:33 -0500 (EST) Message-Id: <199811250844.DAA27850@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Resend Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to track a problem where a "write()" to a socket sends the beginning of the data over and over. I'm looking at "sosend()" in uipc_socket.c, a comment says: > * Returns nonzero on error, timeout or signal; callers > * must check for short counts if EINTR/ERESTART are returned. > * Data and control buffers are freed on return. However, I don't see anywhere in the code where it returns EINTR/ERESTART. That is, if this code mistakenly loops when it gets interrupted or does a partial write(), it would result in the behavior I am seeing. That is: When asked to write a big buffer "1234", we are sometimes seeing on the network connection: "1121231234" Any ideas? -Rob ps. Sorry for all the questions and issues. I'm trying to help the best I can given my new-ness to the FreeBSD internals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message