From owner-freebsd-current Tue Mar 25 18:48:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA07404 for current-outgoing; Tue, 25 Mar 1997 18:48:24 -0800 (PST) Received: from hobbes.saturn-tech.com (drussell@[207.229.19.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07320 for ; Tue, 25 Mar 1997 18:46:59 -0800 (PST) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id TAA22296; Tue, 25 Mar 1997 19:46:58 -0700 (MST) Date: Tue, 25 Mar 1997 19:46:57 -0700 (MST) From: Doug Russell To: freebsd-current@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: SIGTERMs killing X In-Reply-To: <199703252328.QAA26225@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Mar 1997, Terry Lambert wrote: > I'm not sure whether SIGTERM should ever be sent, actually... I guess > it can't hurt, considering it's default is to terminate the process. All this talk of signals reminds me of a (totally) unrelated problem one of my machines seems to be having lately..... My main workstation, which usually runs X all the time, has exited on a sig 6 from X a couple times in the last few days for no apparent reason. Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 Mar 25 11:27:22 586quick166 /kernel: pid 7136 (XF86_SVGA), uid 0: exited on signal 6 I can't for the life of me determine why it would have got an ABORT signal.... Where would that be coming from? The machine is just sitting there idle (AFAIK, anyway... :)) and when I get home from work, for example, it's no longer running X. Anyone else had any kind of similar problem, or any idea how I can figure out where these are coming from?? It is rather annoying. :) Later......