From owner-freebsd-current Thu Oct 15 13:06:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21233 for freebsd-current-outgoing; Thu, 15 Oct 1998 13:06:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21227 for ; Thu, 15 Oct 1998 13:06:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01067; Thu, 15 Oct 1998 13:10:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810152010.NAA01067@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Darin Slovitt cc: freebsd-current@FreeBSD.ORG Subject: Re: Limits Problems ... In-reply-to: Your message of "Thu, 15 Oct 1998 10:09:31 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Oct 1998 13:10:14 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a known bug in 3.0, most commonly affecting laptop users. We haven't been able to track down the exact cause of it. > I been looking through the mailing archives, but I couldn't find a direct > answer to my problem. Perhaps someone here will be helpfull, and please > excuse this post if I missed some obvious answer ... > > I have installed a fresh copy of 3.0-19981006-BETA, and seem to have no > end of problems with limits. When I run 'limits', I get the following > results: > > Resource limits (current): > cputime infinity secs > filesize infinity kb > datasize 524288 kb > stacksize 65536 kb > coredumpsize infinity kb > memoryuse infinity kb > memorylocked infinity kb > maxprocesses 531 > openfiles 1064 > > I have checked login.conf, and it does indeed confirm that the cputime > limits should be set to 'infinity'. > > :cputime=unlimited:\ > :datasize=unlimited:\ > :stacksize=unlimited:\ > :memorylocked=unlimited:\ > :memoryuse=unlimited:\ > :filesize=unlimited:\ > :coredumpsize=unlimited:\ > :openfiles=unlimited:\ > :maxproc=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 > > The point at which this occurs seems random at best, sometimes I almost > make it to the end, other times only two or so files are extracted > before it gives the above message. > > What am I missing? When you 'su' to root, does it keep the limits of the > current user, or take on the limits set for root? This machine is in a > remote location, and I cannot compile or even untar things! Why would the > installation default to this!? > > Any help would be greatly appreciated!! > > -- > TTYS :-) > Darin Slovitt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message