From owner-freebsd-bugs@FreeBSD.ORG Thu Feb 17 19:20:14 2005 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86AB516A4CE for ; Thu, 17 Feb 2005 19:20:14 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 435BD43D31 for ; Thu, 17 Feb 2005 19:20:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j1HJKEs8087055 for ; Thu, 17 Feb 2005 19:20:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j1HJKEaa087054; Thu, 17 Feb 2005 19:20:14 GMT (envelope-from gnats) Resent-Date: Thu, 17 Feb 2005 19:20:14 GMT Resent-Message-Id: <200502171920.j1HJKEaa087054@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Sandeep Kumar Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9403116A500 for ; Thu, 17 Feb 2005 19:10:22 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7968443D2F for ; Thu, 17 Feb 2005 19:10:22 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j1HJAM3Z039473 for ; Thu, 17 Feb 2005 19:10:22 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j1HJAM6Y039472; Thu, 17 Feb 2005 19:10:22 GMT (envelope-from nobody) Message-Id: <200502171910.j1HJAM6Y039472@www.freebsd.org> Date: Thu, 17 Feb 2005 19:10:22 GMT From: Sandeep Kumar To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: misc/77651: init can loose shutdown related signals X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 19:20:14 -0000 >Number: 77651 >Category: misc >Synopsis: init can loose shutdown related signals >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 17 19:20:13 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Sandeep Kumar >Release: 4.10 >Organization: Juniper Networks >Environment: FreeBSD bbuild26 4.10-PRERELEASE-20040428 FreeBSD 4.10-PRERELEASE-20040428 #0: Tue May 18 11:57:20 PDT 2004 root@bbuild26.juniper.net:/usr/src/sys/compile/bbuild26 i386 >Description: When init receives SIGHUP, the state machine's requested_transition is changed to clean_ttys. Lets say SIGTERM is received while we are in clean_ttys, it will set requested_transition to death. But at the end of clean_ttys it will return multi_user directly which then resets requested_transition. So we loose the SIGTERM sent by shutdown >How-To-Repeat: Create a big /etc/ttys. kill -1 1; shutdown -r now Lot of times the machine will not reboot. >Fix: While returning, clean_ttys should check if requested_transition is no longer clean_ttys and then return requested_transition instead of multi_user >Release-Note: >Audit-Trail: >Unformatted: