From owner-freebsd-stable Wed Oct 14 02:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03734 for freebsd-stable-outgoing; Wed, 14 Oct 1998 02:40:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03728 for ; Wed, 14 Oct 1998 02:40:17 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from nashira (nashira [128.130.111.21]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id LAA14691; Wed, 14 Oct 1998 11:37:37 +0200 (MET DST) Date: Wed, 14 Oct 1998 11:37:35 +0200 (MET DST) From: Gerald Pfeifer To: Wilson Tam cc: stable@FreeBSD.ORG Subject: Re: got SIGFPE exception from xlock In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 14 Oct 1998, Wilson Tam wrote: > I am using 2.2.7 on a K6 machine. I got a problem on xlock, it generates > SIGFPE exception once awhile. It is a serious problem for me because after > the xlock core dump, my terminal become unlock and anyone can use my > account. I'm tempted to believe that this will only happen for selected modes in xlock, probably a xlock bug. A save workaround is to restrict xlock to some fixed mode via the command-line. Worked for us here. Gerald -- Gerald Pfeifer (Jerry) Vienna University of Technology pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message