From owner-freebsd-current Wed Jun 10 02:47:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11108 for freebsd-current-outgoing; Wed, 10 Jun 1998 02:47:52 -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 CAA11088 for ; Wed, 10 Jun 1998 02:47:46 -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 LAA24313; Wed, 10 Jun 1998 11:45:53 +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 19:03:01 +1000." <199806100903.TAA14136@cimlogic.com.au> Date: Wed, 10 Jun 1998 11:45:53 +0200 Message-ID: <24311.897471953@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199806100903.TAA14136@cimlogic.com.au>, John Birrell writes: >Bob Bishop wrote: >> >Signal 24 is SIGXCPU (exceeded CPU time limit). Check your ulimit >> >settings ("limit" if you use csh) and your login.conf setup. >> >> # limit >> cputime unlimited >> [etc] >> >> Checked that before showing my head above the parapet; and I did say >> "Doesn't seem to be repeatable" :-) > >FWIW, ditto (an occasional SIGXCPU), ditto (unlimited cputime) and ditto >(doesn't seem repeatable). Are you running anything that might be fiddling the clock ? xntpd or timed ? -- 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