From owner-freebsd-current@FreeBSD.ORG Wed Aug 31 20:26:24 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDEF616A41F; Wed, 31 Aug 2005 20:26:24 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E4C643D45; Wed, 31 Aug 2005 20:26:24 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (Xserve/8.12.11/smtpout05/MantshX 4.0) with ESMTP id j7VKQNhd013443; Wed, 31 Aug 2005 13:26:24 -0700 (PDT) Received: from [10.1.1.209] (nfw1.codefab.com [199.103.21.225]) (authenticated bits=0) by mac.com (Xserve/smtpin01/MantshX 4.0) with ESMTP id j7VKQLSm026003; Wed, 31 Aug 2005 13:26:22 -0700 (PDT) In-Reply-To: <20050831194612.GG32477@odin.ac.hmc.edu> References: <20050831120730.B39418@fledge.watson.org> <20050831194612.GG32477@odin.ac.hmc.edu> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <932461F5-1E5B-4E6C-9109-97A54C128EE5@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 31 Aug 2005 16:26:17 -0400 To: Brooks Davis X-Mailer: Apple Mail (2.734) Cc: Robert Watson , current@freebsd.org Subject: Re: Ctrl-c abort of dhclient during rc.d start aborts all network configuration X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 20:26:24 -0000 On Aug 31, 2005, at 3:46 PM, Brooks Davis wrote: >> (2) If a dhclient is ctrl-c'd, it would be nice if the rest of the >> network >> configuration continued. > > I don't see any code in the startup scripts that would cause them to > exit on failure so the issue is probalby that the signal is being > delivered to the /etc/rc.d/netif instance. I don't really know > what the > solution to that is. Add: trap "" 2 3 ...to the beginning of /etc/rc.d/netif, and a "trap 2 3" at the end, so the shell ignores SIGQUIT (aka Control-C)? -- -Chuck