From owner-freebsd-questions Wed Sep 15 11: 4:42 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rdc1.az.home.com (ha1.rdc1.az.home.com [24.1.240.66]) by hub.freebsd.org (Postfix) with ESMTP id 178E715347 for ; Wed, 15 Sep 1999 11:04:39 -0700 (PDT) (envelope-from lrmoore@home.com) Received: from patches ([24.1.238.229]) by mail.rdc1.az.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19990915180439.WWZK25900.mail.rdc1.az.home.com@patches> for ; Wed, 15 Sep 1999 11:04:39 -0700 Message-ID: <000801beffa5$0108e740$e5ee0118@chnd1.az.home.com> From: "Rick Moore" To: Subject: Hung sockets which leads to pthread question... Date: Wed, 15 Sep 1999 11:06:16 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BEFF6A.5477DBB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BEFF6A.5477DBB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm writing an internet application, and occasionally the sockets lock = up during read with no apparent time out. I've seen the same thing = happen under FreeBSD, Linux, and Windows NT, with various motherboards, = NIC cards, and ISPs. Bottom line: I have to deal with it. setsockopt with a RECV_TIMEOUT (<- I forget the exact syntax, please = excuse my script) doesn't appear to work. I need to be able to kill or interrupt a thread when it gets in this = state. FreeBSD doesn't seem to support pthread_cancel(). Although = signal functionality appears to exist, it doesn't seem to work using = sigaction() and pthread_kill(). I can't be the only person in the universe to deal with this. Does = anybody have some advice? Please respond directly or at least copy my = email address above. Regards, Rick ------=_NextPart_000_0005_01BEFF6A.5477DBB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm writing an internet application, and = occasionally the=20 sockets lock up during read with no apparent time out.  I've seen = the same=20 thing happen under FreeBSD, Linux, and Windows NT, with various = motherboards,=20 NIC cards, and ISPs.  Bottom line: I have to deal with = it.
 
setsockopt with a RECV_TIMEOUT (<- I forget the = exact=20 syntax, please excuse my script) doesn't appear to work.
 
I need to be able to kill or interrupt a thread when = it gets=20 in this state.  FreeBSD doesn't seem to support = pthread_cancel(). =20 Although signal functionality appears to exist, it doesn't seem to work = using=20 sigaction() and pthread_kill().
 
I can't be the only person in the universe to deal = with=20 this.  Does anybody have some advice?  Please respond directly = or at=20 least copy my email address above.
 
Regards,
Rick
 
 
------=_NextPart_000_0005_01BEFF6A.5477DBB0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message