Date: Wed, 10 Jun 1998 11:45:53 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Birrell <jb@cimlogic.com.au> Cc: rb@gid.co.uk (Bob Bishop), jdp@polstra.com, current@FreeBSD.ORG Subject: Re: Spurious SIGXCPU Message-ID: <24311.897471953@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 10 Jun 1998 19:03:01 %2B1000." <199806100903.TAA14136@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24311.897471953>