From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Owens Date: Wed, 20 Apr 2005 00:04:09 +0000 Subject: Re: [PATCH] salinfo_decode silent exit in older 2.4s Message-Id: <16928.1113955449@ocs3.ocs.com.au> List-Id: References: <1112995423.7189.133.camel@krebs.dannf> In-Reply-To: <1112995423.7189.133.camel@krebs.dannf> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-ia64@vger.kernel.org On Tue, 19 Apr 2005 15:51:28 -0600, dann frazier wrote: >On Wed, 2005-04-13 at 13:51 -0600, dann frazier wrote: >> On Tue, 2005-04-12 at 09:03 +1000, Keith Owens wrote: >> > I coded that exit on the assumption that the only reason salinfo_decode >> > would get -EINTR is from a signal. salinfo_decode 0.7 does not have >> > alarms, so the only signal should be from an external event, i.e. when >> > the user wants to shut it down. Before changing the behaviour, can you >> > find out why -EINTR is being returned in the first place. IOW, what >> > event is causing -EINTR to be returned. >> >> hey Keith, >> An strace shows a SIGCHLD, for which a handler is registered. >> Apparently this is the salinfo_decode_oem process? > >hey Keith, > Did this reply answer your question, or do you need more information >from me? It seems SIGCHLD is the corner case. Does exit(0) make sense >for other signals? Thanks, you answered my questions. I have a lot of updates queued for salinfo_decode to make it more resilient, your patch has been included in that set, which I am stil testing.