From owner-freebsd-current Thu Oct 15 09:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16544 for freebsd-current-outgoing; Thu, 15 Oct 1998 09:28:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16537 for ; Thu, 15 Oct 1998 09:28:29 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA22910; Thu, 15 Oct 1998 09:28:10 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 15 Oct 1998 09:28:09 -0700 (PDT) From: Doug White To: Darin Slovitt cc: freebsd-current@FreeBSD.ORG Subject: Re: Limits Problems ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Oct 1998, Darin Slovitt wrote: > 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. Don't forget, when you modfiy /etc/login.conf, run cap_mkdb afterwards. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message