From owner-freebsd-questions Thu Jun 10 12:51: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from enws626.eas.asu.edu (modem-1177.rns.tamu.edu [165.91.68.216]) by hub.freebsd.org (Postfix) with ESMTP id 63D3E14E6A for ; Thu, 10 Jun 1999 12:50:55 -0700 (PDT) (envelope-from limanond@enws626.eas.asu.edu) Received: (from limanond@localhost) by enws626.eas.asu.edu (8.8.7/8.8.7) id OAA10005; Thu, 10 Jun 1999 14:54:55 GMT (envelope-from limanond) Message-ID: <19990610145455.33587@lymatech.com> Date: Thu, 10 Jun 1999 14:54:55 +0000 From: Suttipan Limanond To: freebsd-questions@FreeBSD.org Subject: Out of Space error from `atrun' Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I was trying to install ATLAS which is a machine-specific optimized BLAS routine on FreeBSD 2.2.5. I tried doing this three times. The first two times failed (screen, keyboard, and mouse frozen up) but the last time was a success. I noticed the following mail from daemon on all those three occasions: "From daemon Thu Jun 10 03:55:18 1999 Date: Thu, 10 Jun 1999 03:55:17 GMT From: root (Cron Daemon) To: root Subject: Cron /usr/libexec/atrun X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: Out of space" Does anyone know what this means? ATLAS installation is very heavy on CPU usage (90+% user, with no idle time). When the machine died, I noticed totally different CPU usage (2-3% user, 95-96% system). So I suspect maybe `atrun' had something to do with installation failure. Thanks very much, Suttipan Limanond. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message