From owner-freebsd-current Wed Jun 10 05:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17296 for freebsd-current-outgoing; Wed, 10 Jun 1998 05:36:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17285 for ; Wed, 10 Jun 1998 05:36:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id OAA24715; Wed, 10 Jun 1998 14:34:43 +0200 (CEST) To: John Birrell cc: rb@gid.co.uk (Bob Bishop), jdp@polstra.com, current@FreeBSD.ORG Subject: Re: Spurious SIGXCPU In-reply-to: Your message of "Wed, 10 Jun 1998 20:58:12 +1000." <199806101058.UAA14492@cimlogic.com.au> Date: Wed, 10 Jun 1998 14:34:42 +0200 Message-ID: <24713.897482082@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199806101058.UAA14492@cimlogic.com.au>, John Birrell writes: >Bob Bishop wrote: >> Hi, >> >> You wouldn't perchance happen to be running anything CPU-intensive in the >> background, nice'd right down? > >Not in the background, but the foreground process is both CPU intensive >and long lived. It's a build program that checks out RCS files, >parses sources, conditionally complies and links, automatically executes >tests - all from a single execution. I've seen this die a few times due to >sig 24. I've just started it after a make world and a kernel build. It >discovers the kernel and compiler/linker are new so it recompiles and >retests everything. If you look with ps does the time consumption look sane for this process ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message