From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 9 05:25:19 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EF56C4BC for ; Wed, 9 Jan 2013 05:25:19 +0000 (UTC) (envelope-from rsharpe@richardsharpe.com) Received: from zmail.servaris.com (zmail.servaris.com [107.6.51.160]) by mx1.freebsd.org (Postfix) with ESMTP id A119B1C8 for ; Wed, 9 Jan 2013 05:25:19 +0000 (UTC) Received: (qmail 62817 invoked by uid 89); 9 Jan 2013 05:25:15 -0000 Received: from unknown (HELO ?192.168.2.23?) (rsharpe@richardsharpe.com@108.225.16.199) by mail.richardsharpe.com with ESMTPA; 9 Jan 2013 05:25:15 -0000 Subject: Re: Is it possible to block pending queued RealTime signals (AIO originating)? From: Richard Sharpe To: Daniel Eischen In-Reply-To: References: <1357608470.6752.22.camel@localhost.localdomain> <50EB888A.2030802@freebsd.org> <1357626838.6752.27.camel@localhost.localdomain> <50EBC480.8000306@freebsd.org> <1357661646.6752.30.camel@localhost.localdomain> <1357686894.6752.37.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Tue, 08 Jan 2013 21:25:13 -0800 Message-ID: <1357709113.8329.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, David Xu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2013 05:25:20 -0000 On Tue, 2013-01-08 at 22:24 -0500, Daniel Eischen wrote: > On Tue, 8 Jan 2013, Daniel Eischen wrote: > > > On Tue, 8 Jan 2013, Richard Sharpe wrote: > > > >> [ ... ] > >> > >> Well, it turns out that your suggestion was correct. > >> > >> I did some more searching and found another similar suggestion, so I > >> gave it a whirl, and it works. > >> > >> Now, my problem is that Jeremy Allison thinks that it is a fugly hack. > >> This means that I will probably have big problems getting a patch for > >> this into Samba. > > > > I don't understand why JA thinks this is a hack. Their current > > method doesn't work, or at least isn't portable. I've tried this > > on Solaris 10, and it works just as it does in FreeBSD. Test > > program included after signature. > > > > $ ./test_sigprocmask > > Sending signal 16 > > Got signal 16, blocked: true > > Blocking signal 16 using method 0 > > Handled signal 16, blocked: false > > > > Sending signal 16 > > Got signal 16, blocked: true > > Blocking signal 16 using method 1 > > Handled signal 16, blocked: true > > Weird - I just tested it on Linux (2.6.18-238.el5) and it works > the same as FreeBSD and Solaris. Am I misunderstanding something? > Is it possible that Samba's code is broken on all platforms? It is possible :-) AIO is off by default in configure. Then, when you switch it on in configure you have to switch it on in the smb.conf.