AM> Thanks for the reply. Any idea why my system is rebooting itself at exactly
Wild guess: because of too low inode limit (should be 2..3 times file limit).
Somebody should check what happens if inbode-max is way too low compared to
file-max.
--
Meelis Roos ([EMAIL PROTECTED])
-
To unsubscri
On Wed, Oct 04, 2000 at 11:55:02PM +0300, Matti Aarnio wrote:
> On Wed, Oct 04, 2000 at 09:28:41PM +0200, Magnus Naeslund wrote:
> > From: "Adam McKenna" <[EMAIL PROTECTED]>
>
> > [SNAP]
> >
> > This is what i have in one of our webservers (dual p3 512MB) configuration
> > (in rc.local):
>
On Wed, Oct 04, 2000 at 09:28:41PM +0200, Magnus Naeslund wrote:
> From: "Adam McKenna" <[EMAIL PROTECTED]>
> [SNAP]
>
> This is what i have in one of our webservers (dual p3 512MB) configuration
> (in rc.local):
>
> echo "65536" > /proc/sys/fs/file-max
> echo "262144" > /proc/sys/fs/inode
From: "Adam McKenna" <[EMAIL PROTECTED]>
> Hello, I have a system here that was up for over 100 days, using kernel
> 2.2.15. We are running Oracle 8i on it. The middle of last week, we ran
out
> of file handles, so I increased /proc/sys/fs/file-max to 16384 and
> /proc/sys/fs/inode-max to 16384.
4 matches
Mail list logo