Date: Thu, 18 Jun 1998 14:59:24 +1000 (EST) From: John Birrell <jb@cimlogic.com.au> To: krewat@erols.com (Arthur Krewat) Cc: hackers@FreeBSD.ORG Subject: Re: stuck in a recv/read call? Message-ID: <199806180459.OAA13497@cimlogic.com.au> In-Reply-To: <35889915.15FB7483@erols.com> from Arthur Krewat at "Jun 18, 98 00:35:33 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806180459.OAA13497>