From owner-freebsd-questions Fri Nov 8 11:35:16 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03447 for questions-outgoing; Fri, 8 Nov 1996 11:35:16 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA03442 for ; Fri, 8 Nov 1996 11:35:12 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id LAA16914; Fri, 8 Nov 1996 11:34:48 -0800 (PST) Date: Fri, 8 Nov 1996 11:34:48 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: John Duncan cc: Bill Harrison , questions@FreeBSD.ORG Subject: Re: Dumb Question In-Reply-To: <32835195.41C67EA6@pitt.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 8 Nov 1996, John Duncan wrote: > > What does a message from the kernel mean when it "exits on signal 1" > > It means you caught a SIGHUP, a hangup signal. Other things generate > hangups as well. The application usually exits fine with those. > > On a different note, for others who read this message, why do SIGTERM > and SIGKILL work nicely, but a SIGQUIT, which sounds nice and all, dump > core most of the time? Because the apps you may be using may handle SIGTERM and SIGKILL nicely, but not SIGQUIT; the default action on SIGQUIT is to core dump. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major