I had the same issue.
increasing the maxuser in the kernel and recompiling was the answer.
- Original Message -
From: Ruben de Groot [EMAIL PROTECTED]
To: aSe [EMAIL PROTECTED]
Cc: FreeBSD-Questions [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 7:52 AM
Subject: Re: Too many files
At 07:43 AM 2.4.2003 +0100, Ruben de Groot wrote:
On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed:
This is not a matter of diskspace. The kernel holds a fixed length table
in memory with all open files. If this table gets full it usually means
one of two things:
1) You have a runaway
At 07:43 AM 2.4.2003 +0100, Ruben de Groot wrote:
On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed:
This is not a matter of diskspace. The kernel holds a fixed length table
in memory with all open files. If this table gets full it usually means
one of two things:
1) You have a runaway
Hi Gordon,
On Sun, Feb 02, 2003 at 06:16:26PM -0500, aSe typed:
Recently, one of the machines I help to admin ran into problems and had to be
rebooted.
The machine uptime was about 40days and one of the techs told me it became
unresponsive and any command he typed into term it responded Too
At 02:52 PM 2.3.2003 +0100, Ruben de Groot wrote:
Hi Gordon,
On Sun, Feb 02, 2003 at 06:16:26PM -0500, aSe typed:
Recently, one of the machines I help to admin ran into problems and had
to be rebooted.
The machine uptime was about 40days and one of the techs told me it
became unresponsive and
This is not a matter of diskspace. The kernel holds a fixed length table
in memory with all open files. If this table gets full it usually means
one of two things:
1) You have a runaway application, opening way too many files. Identify
the application and fix or disable it.
2) You're running a
On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed:
This is not a matter of diskspace. The kernel holds a fixed length table
in memory with all open files. If this table gets full it usually means
one of two things:
1) You have a runaway application, opening way too many files. Identify
