Re: strange errors on RH7.0

2001-05-14 Thread Sagi Bashari
chael'" <[EMAIL PROTECTED]>; "linux ILUG" > <[EMAIL PROTECTED]> > Sent: Sunday, May 13, 2001 5:03 PM > Subject: RE: strange errors on RH7.0 > > > > Hi, > > > > You don't have to recompile your kernel to increase the max openfiles &g

Re: strange errors on RH7.0

2001-05-13 Thread baryudin
> Hi All > > So to boot the RH7 with 32768 Max files I need to add al line to the > rc.local ? It's a good place > Why RH Team choose to put 4096 and not 32768 ( what is the drawback of > putting larger number ) The first figure is more than enough for an average stand alone system. Larger nu

Re: strange errors on RH7.0

2001-05-13 Thread Ben-Nes Michael
ot; <[EMAIL PROTECTED]> Cc: "'Ben-Nes Michael'" <[EMAIL PROTECTED]>; "linux ILUG" <[EMAIL PROTECTED]> Sent: Sunday, May 13, 2001 5:03 PM Subject: RE: strange errors on RH7.0 > Hi, > > You don't have to recompile your kernel to increas

RE: strange errors on RH7.0

2001-05-13 Thread Boaz Rymland
Ah ! but he might still need to recompile to add /proc FS suport !... ;-) (just being picky...) > -Original Message- > From: Sagi Bashari [SMTP:[EMAIL PROTECTED]] > Sent: Sun 13 May 2001 16:03 > To: Boaz Rymland > Cc: 'Ben-Nes Michael'; linux ILUG > Subj

RE: strange errors on RH7.0

2001-05-13 Thread Sagi Bashari
Hi, You don't have to recompile your kernel to increase the max openfiles number- just change the value in /proc/sys/fs/file-max (ie. echo 32768 > /proc/sys/fs/file-max) Sagi On Sun, 13 May 2001, Boaz Rymland wrote: > Well, it's seems like it is what it says it is... "too many open files in >

Re: strange errors on RH7.0

2001-05-13 Thread Ilya Konstantinov
On Sun, May 13, 2001 at 04:04:19PM +0300, Ben-Nes Michael wrote: > While doing some jobs on the server i got the folowing errors for a few min > ( couldnt do anything ). > After few minutes the shell was active again. There was an errarta notice for plain RedHat 7.0 about RedHat's up2date service

RE: strange errors on RH7.0

2001-05-13 Thread Boaz Rymland
Well, it's seems like it is what it says it is... "too many open files in system"... :-) . You have a limit of the number of open file handles in your system , as well as number of processes, etc' etc' limits to their kinds... . There might be a way to change this in the shell ("ulimit" ?), but y