From owner-freebsd-hackers Fri Jan 29 00:14:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10914 for freebsd-hackers-outgoing; Fri, 29 Jan 1999 00:14:47 -0800 (PST) (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 AAA10903 for ; Fri, 29 Jan 1999 00:14:42 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA13146; Fri, 29 Jan 1999 19:14:15 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199901290814.TAA13146@cimlogic.com.au> Subject: Re: select and threads again In-Reply-To: from "Sergey S. Kosyakov" at "Jan 29, 1999 11: 6:21 am" To: ks@itp.ac.ru (Sergey S. Kosyakov) Date: Fri, 29 Jan 1999 19:14:15 +1100 (EST) Cc: jb@cimlogic.com.au, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Sergey S. Kosyakov wrote: > Thank you for your quick answer. But there is problem with ILU I trying to > solve. For each operation on each TCP socket ILU starts new thread, which > inturn calls select(). I trace this processes and found that if two threads in > the same time calls select (with timeout=infinity) on different sockets that > only the last thread stays operational. The first thread hangs forever on > select(). May be there are some underwater stones? I compile and link ILU with > "cc -g -pthread", nothing more. I have applications (including one I'm working on) that do this a *lot*. It works for me. -- 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