From owner-freebsd-current  Wed Apr  9 10:48:20 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA04239
          for current-outgoing; Wed, 9 Apr 1997 10:48:20 -0700 (PDT)
Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04234
          for <freebsd-current@freebsd.org>; Wed, 9 Apr 1997 10:48:18 -0700 (PDT)
Received: from localhost (taob@localhost)
          by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP
	  id NAA22647; Wed, 9 Apr 1997 13:46:52 -0400 (EDT)
Date: Wed, 9 Apr 1997 13:46:52 -0400 (EDT)
From: Brian Tao <taob@nbc.netcom.ca>
To: Frank Chen Hsiung Chan <frankch@waru.life.nthu.edu.tw>
cc: FREEBSD-CURRENT-L <freebsd-current@freebsd.org>
Subject: Re: XFree86 3.2 causes constant 1.0 load average?
In-Reply-To: <Pine.BSF.3.95q.970407081125.5202A-100000@waru.life.nthu.edu.tw>
Message-ID: <Pine.GSO.3.95.970409134504.18937c-100000@tor-adm1.nbc.netcom.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 7 Apr 1997, Frank Chen Hsiung Chan wrote:
> 
> We had this problem here. We then found that the asclock is
> responsible for this. Try not running asclock and/or other asstuff,
> that might help.

    I really like asclock though, but the bogus load average does not
always occur (even though asclock is always running).  Right now my
load is reported as 0.04.  I'll have to make a log of what I do in a
typical X session and see if that correlates with the load.
-- 
Brian Tao (BT300, taob@netcom.ca)
"Though this be madness, yet there is method in't"