From owner-freebsd-hackers  Sun Nov 24 00:20:00 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA03426
          for hackers-outgoing; Sun, 24 Nov 1996 00:20:00 -0800 (PST)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA03418
          for <hackers@freebsd.org>; Sun, 24 Nov 1996 00:19:52 -0800 (PST)
Received: from misery.sdf.com ([204.244.213.33]) by misery.sdf.com with SMTP id <1344-9453>; Sun, 24 Nov 1996 00:20:08 -0800
Date: 	Sun, 24 Nov 1996 00:19:59 -0800 (PST)
From: Tom Samplonius <tom@sdf.com>
To: hackers@freebsd.org
Subject: "limit" strangeness
Message-ID: <Pine.NEB.3.94.961124001433.9989A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  This is weird.  The soft limit for "datasize" is larger than the hard
limit.  The softlimit amount for "datasize" coresponds to the MAXDSIZ and
DFLDSIZ param in my kernel config.  But what sets the hard limit size?  Is
the hard limit based on MAXMEM (system has 128M)?  Isn't MAXMEM supposed
to indicate the amount of physical memory?

Script started on Sun Nov 24 00:19:19 1996
atlas# limit
cputime 	unlimited
filesize 	unlimited
datasize 	195312 kbytes
stacksize 	8192 kbytes
coredumpsize 	unlimited
memoryuse 	63496 kbytes
memorylocked 	42333 kbytes
maxproc 	256 
openfiles 	512 
atlas# limit -h
cputime 	unlimited
filesize 	unlimited
datasize 	131072 kbytes
stacksize 	65536 kbytes
coredumpsize 	unlimited
memoryuse 	unlimited
memorylocked 	127000 kbytes
maxproc 	unlimited
openfiles 	unlimited
atlas# whoami
root
atlas# 


Tom