From owner-freebsd-current Fri Oct 3 01:08:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA29245 for current-outgoing; Fri, 3 Oct 1997 01:08:17 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA29238; Fri, 3 Oct 1997 01:08:06 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id BAA22162; Fri, 3 Oct 1997 01:07:37 -0700 (PDT) Message-ID: <19971003010737.54157@hydrogen.nike.efn.org> Date: Fri, 3 Oct 1997 01:07:37 -0700 From: John-Mark Gurney To: Matthew Thyer Cc: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. References: <34348712.F0962930@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <34348712.F0962930@dsto.defence.gov.au>; from Matthew Thyer on Fri, Oct 03, 1997 at 03:18:02PM +0930 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Matthew Thyer scribbled this message on Oct 3: > Does anyone else have this problem or can anyone confirm that it > will be solved by a newer incarnation of -CURRENT or a newer > xlockmore ? don't worry.. I have the same problem.. and my processor is a amd k5-90, and I'm pretty sure I saw it on my amd5x86-133... I think it's just a programming error.... of course I'm running it on a 2.2.1-R.. ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD