From owner-freebsd-hackers Thu Jan 28 06:03:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19423 for freebsd-hackers-outgoing; Thu, 28 Jan 1999 06:03:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from itp.ac.ru (itp.ac.ru [193.233.32.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19414 for ; Thu, 28 Jan 1999 06:03:37 -0800 (PST) (envelope-from ks@itp.ac.ru) Received: from speecart.chg.ru (speecart.chg.ru [193.233.46.2]) by itp.ac.ru (8.9.1/8.9.1) with ESMTP id RAA03456 for ; Thu, 28 Jan 1999 17:07:11 +0300 (MSK) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 28 Jan 1999 17:04:18 +0300 (MSK) Organization: Landau Institute for Theoretical Physics From: "Sergey S. Kosyakov" To: freebsd-hackers@FreeBSD.ORG Subject: select(2) and threads Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, it seems that calling select in more than one concurrent thread cause all such threads except the last to block forever. The same situation is with poll(). The only case when select() and poll() work is when timeout is set to 0. Is select really thread safe in FreeBSD? FreeBSD 3.0-RELEASE Sergey. ---------------------------------- --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message