From owner-freebsd-current Wed Jun 10 13:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09606 for freebsd-current-outgoing; Wed, 10 Jun 1998 13:41:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from auchroisk.pdl.cs.cmu.edu (AUCHROISK.PDL.CS.CMU.EDU [128.2.189.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09558 for ; Wed, 10 Jun 1998 13:40:55 -0700 (PDT) (envelope-from dpetrou@auchroisk.pdl.cs.cmu.edu) Received: (from dpetrou@localhost) by auchroisk.pdl.cs.cmu.edu (8.8.8/8.8.8) id QAA07676 for freebsd-current@freebsd.org; Wed, 10 Jun 1998 16:40:53 -0400 (EDT) (envelope-from dpetrou) From: David Petrou Message-Id: <199806102040.QAA07676@auchroisk.pdl.cs.cmu.edu> Subject: ulimit... To: freebsd-current@FreeBSD.ORG Date: Wed, 10 Jun 1998 16:40:52 -0400 (EDT) Reply-To: dpetrou@cs.cmu.edu X-Mailer: ELM [version 2.4ME+ PL40 (25)] 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 (Sorry if I'm writing to the wrong FreeBSD list. "current" seems the most applicable to me...) > Signal 24 is SIGXCPU (exceeded CPU time limit). Check your ulimit > settings ("limit" if you use csh) and your login.conf setup. Have you guys considered turning off limits by default? It seems that every FreeBSDer at one time or another is bit by this (including me). There must have been at least 50 questions on the FreeBSD lists from people wondering why they get SIGXCPU, "out of memory", etc. If they were off by default, this problem wouldn't exist. And for those that do want to turn them on, they can customize login.conf based on their system's resources, such as amount of RAM, number of users, etc. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message