From owner-freebsd-current Wed Mar 26 17:04:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA18552 for current-outgoing; Wed, 26 Mar 1997 17:04:57 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA18539 for ; Wed, 26 Mar 1997 17:04:52 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA29306; Wed, 26 Mar 1997 17:50:32 -0700 From: Terry Lambert Message-Id: <199703270050.RAA29306@phaeton.artisoft.com> Subject: Re: SIGTERMs killing X To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Wed, 26 Mar 1997 17:50:32 -0700 (MST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org In-Reply-To: <199703270024.LAA01805@rf900.physics.usyd.edu.au> from "David Dawes" at Mar 27, 97 11:24:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> > That would be a bus error, not an abort. > >> > >> That's Terry not understanding nor reading the Xserver sources. > > > >I don't know which X server he is running. > > > >Neither do you. > > I can make a good guess because in the original message where the > kernel messages were shown, the name of the executable dying with > signal 6 was XF86_SVGA: > > Mar 24 12:22:23 586quick166 /kernel: pid 218 (XF86_SVGA), uid 0: exited on signal 6 I stand corrected. I apparently didn't carry enough context forward. Under what normal operational circumstances could this happen? (ie: any known bugs?). If there aren't any, then the fact that it didn't happen before but does now points at FreeNSD, not a X. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.