From owner-freebsd-questions Mon Aug 19 1:19:20 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A58637B400 for ; Mon, 19 Aug 2002 01:19:19 -0700 (PDT) Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63FDA43E77 for ; Mon, 19 Aug 2002 01:19:18 -0700 (PDT) (envelope-from garyj@jennejohn.org) Received: from fwd11.sul.t-online.de by mailout08.sul.t-online.com with smtp id 17ghkq-0003wr-0B; Mon, 19 Aug 2002 10:19:16 +0200 Received: from peedub.jennejohn.org (520017439985-0001@[217.235.122.104]) by fmrl11.sul.t-online.com with esmtp id 17ghkf-0qmHzsC; Mon, 19 Aug 2002 10:19:05 +0200 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.5/8.11.6) with ESMTP id g7J8JBPL084938; Mon, 19 Aug 2002 10:19:22 +0200 (CEST) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200208190819.g7J8JBPL084938@peedub.jennejohn.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3 To: jau@iki.fi Cc: freebsd-questions@freebsd.org Subject: Re: O_ASYNC + SIGIO does not seem to work for UNIX domain sockets Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 19 Aug 2002 00:49:17 +0300." <200208182149.AAA29911@cs78135006.pp.htv.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Aug 2002 10:19:11 +0200 From: Gary Jennejohn X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jukka A. Ukkonen writes: > > Hi all, > > Has anyone experienced the same problem as I seem to have > noticed? > I tried using O_ASYNC fcntl flag and a SIGIO handler to find > out when a UNIX domain socket has got something to read while > my code has bee sitting in sigsuspend(). The SIGIO patently > *never* arrives, though a lot data has been written to the > other end of the socket. > While sitting in the same sigsuspend() SIGINT, SIGTERM, and > SIGCHLD all get delivered as they should. So, it seems that > this is somehow related to the UNIX domain sockets only. > If you have seen the O_ASYNC/FIOASYNC + SIGIO working with > Internet sockets or terminal lines, it means nothing in my > case. > I have seen this happen only with the UNIX domain sockets. > > Any information, similar experiences, or bug fixes would be > very welcome. > Since you didn't say I'll ask - did you do F_SETOWN on the socket ? --- Gary Jennejohn / garyj@jennejohn.org gj@freebsd.org gj@denx.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message