From owner-freebsd-smp Thu Apr 8 19: 5:57 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 3420314DA4 for ; Thu, 8 Apr 1999 19:05:48 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA12221; Thu, 8 Apr 1999 20:22:18 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd012199; Thu Apr 8 20:22:06 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id TAA14310; Thu, 8 Apr 1999 19:03:33 -0700 (MST) From: Terry Lambert Message-Id: <199904090203.TAA14310@usr04.primenet.com> Subject: Re: concurrent select()s on listen socket broken under SMP To: barney@databus.com (Barney Wolff) Date: Fri, 9 Apr 1999 02:03:33 +0000 (GMT) Cc: smp@FreeBSD.ORG In-Reply-To: <370d0b3a0.466c@databus.databus.com> from "Barney Wolff" at Apr 8, 99 03:59:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Seems to me you need to set the socket non-blocking, and then handle > the EWOULDBLOCK on the fd that loses. I don't think this should be > considered a kernel error. It's SMP specific. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message