From owner-freebsd-stable@freebsd.org Sat Mar 19 01:47:02 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41911AD5158 for ; Sat, 19 Mar 2016 01:47:02 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::3001]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow 2014 CA Root Certificate" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7091B62 for ; Sat, 19 Mar 2016 01:47:00 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801:0:0:0:4001]) by mta1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPS id u2J1ksXl008339 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 19 Mar 2016 12:46:54 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1458352014; bh=/oG9XGAJ/QV7TQKwjz/z9c9L8D76FGMyDzXlV2BYpgo=; h=Date:From:To:Subject; b=HF1xNqezojyzuODtsCOoVQXxn6VkPvCGOk9DCdiuDeDm1NR7h7s0SGxKUDCUyF9AV ahCB7ziHTMBmxlqf0ce/ireT7WzeX+zlOd2G1qWREArM00E0tUPBFSP3RheygijULN P4jibRYEr0E06eyM+esW2VuZHCKN1jaFjqElG74w= Received: from rwpc16.gfn.riverwillow.net.au (rwpc16.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:ae87:a3ff:fe04:b351]) (authenticated bits=56) by mail1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPSA id u2J1kqSF008338 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 19 Mar 2016 12:46:53 +1100 (AEDT) Date: Sat, 19 Mar 2016 12:46:50 +1100 From: John Marshall To: freebsd-stable@FreeBSD.org Subject: 10.3-RC3 kill -TERM weirdness after upgrade Message-ID: <20160319014650.GA10652@rwpc16.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 01:47:02 -0000 I've just upgraded two local servers from 10.3-RC2 to 10.3-RC3. One is i386 (Pentium 4) with 1.5GB memory; the other is amd64 (Xeon E5 x 2) with 16GB. Something seems to be swallowing SIGTERM sometimes. I've never seen this before. rc scripts and service(8) hang when trying to stop some services. If I break out of the script or service command (via ctrl-C) and invoke kill(1), passing the relevant PID, the shell prompt returns immediately but the process doesn't terminate. Sending SIGKILL to the process via kill(1) does its job. I am seeing this with: squid (on both servers) ircd-ratbox (on both servers) git_daemon I am not seeing this (all seems normal) with: cupsd sendmail (on both servers) Is anybody else seeing this, or have I been bitten by some other coincidence? -- John Marshall