From owner-freebsd-hackers Fri May 22 14:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17218 for freebsd-hackers-outgoing; Fri, 22 May 1998 14:08:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@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 OAA17149 for ; Fri, 22 May 1998 14:08:14 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id RAA05684; Fri, 22 May 1998 17:06:57 -0400 (EDT) Date: Fri, 22 May 1998 17:06:57 -0400 (EDT) Message-Id: <199805222106.RAA05684@highwind.com> From: HighWind Software Information To: jb@cimlogic.com.au CC: jb@cimlogic.com.au, freebsd-hackers@FreeBSD.ORG, support@highwind.com In-reply-to: <199805222107.HAA13138@cimlogic.com.au> (message from John Birrell on Sat, 23 May 1998 07:07:16 +1000 (EST)) Subject: Re: FreeBSD 2.2.6 + pthread == write() bug Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, A customer of ours pointed out that FreeBSD 3.0's uthread_write.c has a "_thread_kern_sig_block(&status);" in there as well. Unknown if that is the issue. I also believe that write() calls are returning "EAGAIN" sometimes and writing data. It is supposed to return EAGAIN and have written NO data. That way, when you retry the write() call, it doesn't resend the same data. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message