From owner-freebsd-current  Wed Jun 10 02:12:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA05306
          for freebsd-current-outgoing; Wed, 10 Jun 1998 02:12:52 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05296;
          Wed, 10 Jun 1998 02:12:40 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA05983;
	Wed, 10 Jun 1998 19:12:33 +1000
Date: Wed, 10 Jun 1998 19:12:33 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199806100912.TAA05983@godzilla.zeta.org.au>
To: jdp@polstra.com, rb@gid.co.uk
Subject: Re: Spurious SIGXCPU
Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>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" :-)

Apparently your process appeared to run for a negative amount of time.
p_runtime is unsigned (64 bits), so negative runtimes are interpreted
as huge runtimes, even huger than RLIMIT_INFINITY.  This bug used to
be avoided by using signed variables even to hold values that should
be non-negative.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message