From owner-freebsd-hackers Wed Jun 17 21:53:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16761 for freebsd-hackers-outgoing; Wed, 17 Jun 1998 21:53:42 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16746 for ; Wed, 17 Jun 1998 21:53:36 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id OAA13497; Thu, 18 Jun 1998 14:59:24 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199806180459.OAA13497@cimlogic.com.au> Subject: Re: stuck in a recv/read call? In-Reply-To: <35889915.15FB7483@erols.com> from Arthur Krewat at "Jun 18, 98 00:35:33 am" To: krewat@erols.com (Arthur Krewat) Date: Thu, 18 Jun 1998 14:59:24 +1000 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arthur Krewat wrote: > I have it running under FreeBSD, and after a few problems, got it > working. > > However, after three (yes three and ALWAYS three!) it'll get stuck > in a recv or read (tried both!), sucking up CPU time. With or without > other FD's open, etc. etc. When it hits the third socket, it always > dies with this. > > I know this can be my own code that's killing me and it's something > with the cross-platform thing, but WHAT can cause a read/recv to > spin it's wheels? What version of FreeBSD? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message