From owner-freebsd-commit  Wed Apr  5 08:40:04 1995
Return-Path: commit-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA22918
          for commit-outgoing; Wed, 5 Apr 1995 08:40:04 -0700
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA22899
          for cvs-lib-outgoing; Wed, 5 Apr 1995 08:39:57 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA22881
          ; Wed, 5 Apr 1995 08:39:29 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA23814; Thu, 6 Apr 1995 01:36:31 +1000
Date: Thu, 6 Apr 1995 01:36:31 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504051536.BAA23814@godzilla.zeta.org.au>
To: bde@zeta.org.au, guido@gvr.win.tue.nl
Subject: Re: cvs commit: src/lib/libc/rpc rpc_dtablesize.c
Cc: CVS-commiters@freefall.cdrom.com, cvs-lib@freefall.cdrom.com,
        pritc003@maroon.tc.umn.edu, wpaul@freefall.cdrom.com
Sender: commit-owner@FreeBSD.org
Precedence: bulk

>> 
>> Someone broke this some more by introducing the sysctl variable
>> `kern.maxfilesperproc'.  What systems implement "new" limits?
>> 

>I did to be able to protect yourself against ppl eating up *all*
>files in a system. We've had such jokers, and there is nothing you can do
>about it, except this.

You can hack init or login to set the hard resource limit.

Bruce