Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932305AbVIZQoo (ORCPT ); Mon, 26 Sep 2005 12:44:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751677AbVIZQoo (ORCPT ); Mon, 26 Sep 2005 12:44:44 -0400 Received: from clock-tower.bc.nu ([81.2.110.250]:54942 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751673AbVIZQon (ORCPT ); Mon, 26 Sep 2005 12:44:43 -0400 Subject: RE: Resource limits From: Alan Cox To: Roger Heflin Cc: "'Al Boldi'" , linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 26 Sep 2005 18:11:30 +0100 Message-Id: <1127754691.27757.26.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 719 Lines: 19 On Llu, 2005-09-26 at 09:44 -0500, Roger Heflin wrote: > While talking about limits, one of my customers report that if > they set "ulimit -d" to be say 8GB, and then a program goes and The kernel doesn't yet support rlimit64() - glibc does but it emulates it best effort. Thats a good intro project for someone > It would seem that the best thing to do would be to abort on > allocates that will by themselves exceed the limit. 2.6 supports "no overcommit" modes. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/