From owner-freebsd-hackers Fri May 11 0:56:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id C614D37B422 for ; Fri, 11 May 2001 00:56:26 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-96-2.netcologne.de [213.168.96.2]) by mr200.netcologne.de (Mirapoint) with ESMTP id AFI37987; Fri, 11 May 2001 09:56:24 +0200 (CEST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.3) with ESMTP id f4B7u8m27867 for ; Fri, 11 May 2001 09:56:08 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 11 May 2001 09:56:08 +0200 (CEST) From: Paul Herman To: Subject: ulimit -b in /bin/sh Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if -arch is a better list for this. If so, followups there. The units for sbsize in limits is currently displayed in bytes, not kilobytes. Changing the output to kb to be consistent with the others (datasize, stacksize, memoryuse, etc.) shouldn't be a problem... The problem would be with "limits -e". Right now, /bin/sh expects sbsize, i.e. "ulimit -b", to be in bytes rather than kilobytes. Ideally, /bin/sh should take "ulimit -b 1024" to mean "set sbsize limit to 1MB", just like "ulimit -m 1024" means "set memoryuse to 1MB." Now, get out your POLA guns. Would this change to /bin/sh be too astonishing? Are we stuck with the way it is now, or is it best to nip it in the bud and change this behavior now? -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message