Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.unix.programmer Subject: Re: OT: Windows (Was: Re: Open Source does not mean easily Date: Tue, 7 Jan 2025 02:14:11 -0000 (UTC) Organization: A noiseless patient Spider Lines: 10 Message-ID: References: <1jSeP.17355$jUJ9.3923@fx08.iad> <677c7a1b$0$28501$426a74cc@news.free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 07 Jan 2025 03:14:11 +0100 (CET) Injection-Info: dont-email.me; posting-host="2d399114ee3fd1158a37c5ed6fa4afe6"; logging-data="2002621"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/+fJNSgvibXDe+4GSUYDU+" User-Agent: Pan/0.161 (Chasiv Yar; ) Cancel-Lock: sha1:4LnXdAkxLcr1Vrs2uEnCZqsP5yA= Bytes: 1692 On 07 Jan 2025 00:49:32 GMT, Nicolas George wrote: > The communication mechanisms between POSIX > threads and Unix I/O are completely alien to each-other: it is not > possible to poll() on a thread condition, nor is it it possible to set > up a condition to be woken by data on a file descriptor. Linux offers signalfd, so you can indeed use poll(2) in a thread to be woken up by any file descriptor, including a signal one (and that includes POSIX real-time signals).