Kris Kennaway wrote:
Having a hard limit is by design, or users could run your machine out
of memory and cause it to panic.
# sysctl -w kern.maxfiles=2
kern.maxfiles: 12328 -> 2
Ok, I agree. Must've confused something here. I was under the impression
that it was fixed at boot. The user iss
On Sun, Jan 02, 2005 at 07:09:35PM +0100, Matthias Buelow wrote:
> Kris Kennaway wrote:
>
> >A truly enormous number :-) You just need to increase the value of
> >kern.maxfiles in /boot/loader.conf as appropriate for your workload.
>
> would it be possible to make this dynamically allocated in th
Kris Kennaway wrote:
A truly enormous number :-) You just need to increase the value of
kern.maxfiles in /boot/loader.conf as appropriate for your workload.
would it be possible to make this dynamically allocated in the future?
imho, such limits are a bit anachronistic.
mkb.
_
On Sun, Jan 02, 2005 at 01:18:56AM -0800, Lucky Green wrote:
> I am running FreeBSD 5.3 on a dual CPU system with 1 GB of RAM with under a
> dozen of very active users and a few rather active processes. The system
> keeps running out of FDs, causing any number of problems, such as preventing
> ssh
I am running FreeBSD 5.3 on a dual CPU system with 1 GB of RAM with under a
dozen of very active users and a few rather active processes. The system
keeps running out of FDs, causing any number of problems, such as preventing
ssh logins.
sysctl kern.maxfiles shows a maximum of 12328 FDs. My kernel
