From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WhFhX-0006ON-Pb for ltp-list@lists.sourceforge.net; Mon, 05 May 2014 10:00:47 +0000 Received: from aserp1040.oracle.com ([141.146.126.69]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WhFhW-0002Oi-U8 for ltp-list@lists.sourceforge.net; Mon, 05 May 2014 10:00:47 +0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s45A0e5s032614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 5 May 2014 10:00:41 GMT Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s45A0dYL027506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 May 2014 10:00:39 GMT Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s45A0dQ8027501 for ; Mon, 5 May 2014 10:00:39 GMT Message-ID: <53676144.20306@oracle.com> Date: Mon, 05 May 2014 14:00:36 +0400 From: Stanislav Kholmanskikh MIME-Version: 1.0 References: <1398419188-17193-1-git-send-email-stanislav.kholmanskikh@oracle.com> In-Reply-To: <1398419188-17193-1-git-send-email-stanislav.kholmanskikh@oracle.com> Subject: Re: [LTP] [PATCH] sigaction 9-1, 10-1, 11-1: use SIGKILL instead of SIGHUP List-Id: Linux Test Project General Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-list-bounces@lists.sourceforge.net To: ltp-list@lists.sourceforge.net Cc: vasily.isaenko@oracle.com Hi! On 04/25/2014 01:46 PM, Stanislav Kholmanskikh wrote: > There are test environments, where the SIGHUP signal may be either > added to the signal mask or ignored. One example of such environments > is Autotest, which sets the SIGHUP signal to SIG_IGN for its jobs. > > Therefore the above test cases hang in that environment because their > parent processes send SIGHUP to terminate the child (and the child ignores it). > > I think it will not be a problem to use SIGKILL here instead of SIGHUP, because > SIGKILL can not be caught, blocked, or ignored. > And it does the job - stopping the child - very well :) > > Signed-off-by: Stanislav Kholmanskikh Could anybody look at this patch, please? Thanks. ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list