From owner-freebsd-current Thu Oct 15 16:35:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27314 for freebsd-current-outgoing; Thu, 15 Oct 1998 16:35:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27304 for ; Thu, 15 Oct 1998 16:35:35 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA29315; Thu, 15 Oct 1998 16:35:13 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd029289; Thu Oct 15 16:35:09 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA26332; Thu, 15 Oct 1998 16:35:06 -0700 (MST) From: Terry Lambert Message-Id: <199810152335.QAA26332@usr04.primenet.com> Subject: Re: Limits Problems ... To: dwhite@resnet.uoregon.edu (Doug White) Date: Thu, 15 Oct 1998 23:35:06 +0000 (GMT) Cc: darin@slovitt.net, freebsd-current@FreeBSD.ORG In-Reply-To: from "Doug White" at Oct 15, 98 09:28:09 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Resource limits (current): > > cputime infinity secs > > > I have checked login.conf, and it does indeed confirm that the cputime > > limits should be set to 'infinity'. > > > > :cputime=unlimited:\ > > > When I attempt to untar a file, I get the ever-so-annoying: > > Cputime limit exceeded > > 0.000u 0.000s 5:33.14 0.0% 0+0k 3594+7617io 0pf+0w > > This sounds like the timewarping clock bug that's been popping up on > systems running APM. If you're using the APM driver try knocking it out > of your kernel. Works on my box, which doesn't have APM, so it's still not APM that's causing this problem. APM was a guess, and the verdict is in: the guess was wrong. > Don't forget, when you modfiy /etc/login.conf, run cap_mkdb afterwards. See the output of his "limit" command: he remembered. I think he's probably upset that, no matter what the root cause of the bug is (besides APM, I mean, since it's probably not that), FreeBSD is claiming that some time_t minus another time_t somewhere in the kernel has exceeded infinity. Since that's logically impossible, the code that's enforcing the limit by killing the process is *broken*, since it's apparently grasping neither logic nor one of the basic tenets of number theory. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message