Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Sep 1999 16:35:22 -0700
From:      Bryan Talbot <btalbot@ucsd.edu>
To:        stable@FreeBSD.ORG
Subject:   Re: kern.maxfiles and kern.maxfilesperproc
Message-ID:  <4.2.0.58.19990921163209.00a49f00@ekimaphost>
In-Reply-To: <Pine.SOL.4.05.9909211616350.16568-100000@luna>
References:  <19990921161540.D49731@forty-two.egroups.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At 04:23 PM 9/21/99 , Kip Macy wrote:
>Thanks. Although having maxfiles == maxfilesperproc might make sense for
>special cases e.g. a machine completely dedicated to one process -- It is
>dangerous at best for the general case. Any malicious program can make a
>machine running FreeBSD non-functional. The default should be set with the
>average user in mind, namely protecting him from himself.
>
>
>                                         -Kip


But adjusting maxfilesperproc > maxfiles won't protect you from a malicious 
process or user any more than having maxfilesperproc == maxfiles.  Just 
fork() or run two (or more) processes that open all the file handles.  Same 
result, right?

-Bryan


=====================================================================
IMPORTANT NOTICE: According to certain suggested versions of the
Grand Unified Theory, the primary particles constituting this
message may decay to nothingness within the next Four Hundred
Million Years.
=====================================================================
          "I think not!" said Descartes, who promptly disappeared.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.19990921163209.00a49f00>