/proc/sys/fs/file-max
Currently default in rh71 is 8192
if you want to double it
do
echo 16386 > /proc/sys/fs/file-max
when you reboot that gets reset so put a statement like that in your
rc.local or something.
/Mikkel Fischer
Johan Burati wrote:
> I get the same error on a RH7.1 system,
> can you tell me where I can change the max open files parameter exactly ?
>
> Thanks,
> Johan
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Patrick Powell
> Sent: Tuesday, August 07, 2001 2:27 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: LPRng: bizzare file locking problem
>
> max open files should be something like 1000 !!! Bigh!!! Huge!!!
>
> Also set just about everything to 'unlimited' on for the daemon.
>
> Patrick
>
> > From [EMAIL PROTECTED] Fri Aug 3 20:32:08 2001
> > Date: Fri, 3 Aug 2001 23:32:06 -0400 (EDT)
> > From: Ryan Novosielski <[EMAIL PROTECTED]>
> > To: Patrick Powell <[EMAIL PROTECTED]>
> > cc: <[EMAIL PROTECTED]>
> > Subject: Re: LPRng: bizzare file locking problem
> >
> > 1) 1.8 -- I downloaded this as a binary package from the HP-UX Porting
> > Centre.
> > 2) HP-UX 11.0 (I seriously doubt that anyone else having this problem is
> > also running HP-UX, however)
> > 3) Apparently, though I will look into the others -- the load balance
> > queue is the only queue that is used enough to cause this. It never
> > happened in my tests, either, but under a reasonable load (like around
> > lunch time at my University), this WILL happen. By increasing the
> > max_files value in the system kernel, we were able to make the problem
> > less of an error and more of a warning. We now get the message, as you can
> > see from the below message (the value of max_files was changed from 80 to
> > 120 over the weekend before July 31) less frequently, and it does not
> > seriously impact the performance of the printing. There are still long
> > delays between jobs (a reasonable sized delay upon receiving that error
> > message usually also), but before the error and delays would happen once
> > every few mins, making printing grind to a halt.
> >
> > ---- _ _ _ _ ___ _ _ _
> > |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin
> > |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
> > \__/ Univ. of Med. and Dent. | IST/ACS - New Jersey Medical School - C630
> >
> > On Fri, 3 Aug 2001, Patrick Powell wrote:
> >
> > >
> > > > From [EMAIL PROTECTED] Thu Aug 2 10:06:06 2001
> > > > From: "Ryan Novosielski" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Subject: LPRng:
> > > > Date: Thu, 2 Aug 2001 12:02:38 -0400
> > > >
> > > > 2001-07-31-10:20:27.225 njmsa ljnlab: Open_gdbm: cannot lock
> 'db.ljnlab' -
> > > > Interrupted system call
> > > > 2001-07-31-10:21:39.141 njmsa ljnlab: Open_dgbm: open of DB file
> 'db.ljnlab'
> > > > failed, File open error
> > > > 2001-07-31-10:22:49.332 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-07-31-10:24:04.723 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-07-31-10:28:30.935 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-07-31-15:10:49.968 njmsa ljnlab: Open_gdbm: cannot lock
> 'db.ljnlab' -
> > > > Interrupted system call
> > > > 2001-07-31-15:11:02.989 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-08-01-08:26:48.675 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-08-02-11:27:42.683 njmsa laser2: Open_dgbm: open of DB file
> 'db.laser2'
> > > > failed, File open error
> > > > 2001-08-02-11:35:40.500 njmsa laser2: Open_dgbm: open of DB file
> 'db.laser2'
> > > > failed, File open error
> > > > 2001-08-02-11:38:56.641 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-08-02-11:42:13.005 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > > 2001-08-02-11:44:11.142 njmsa laser2: Open_dgbm: open of DB file
> 'db.laser2'
> > > > failed, File open error
> > > > 2001-08-02-11:48:42.016 njmsa laser1: Open_dgbm: open of DB file
> 'db.laser1'
> > > > failed, File open error
> > > >
> > > > djnlab is a load-balance queue.
> > > > laser1 and laser2 are subservers.
> > > >
> > > > I know many of us are aware of this type of problem, but has anyone
> had any
> > > > luck in 1) making it not as bad, 2) knowing why this happens?
> > >
> > >
> > > 1. What version of GDB are you using?
> > > 2. What OS and version are you using?
> > > 3. Does it happen ONLY on load sharing queues?
> > >
> > > Note that I cannot get this to happen on the 6 test systems I tried this
> > > on in January.
> > >
> > > Patrick ("The ICBM Interception System designed by B.S. Johnson
> > > has just landed a man on Alpha Centauri. We are with holding payment
> > > for project non-completion.") Powell
> > >
> >
> >
>
> ----------------------------------------------------------------------------
> -
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the
> impatient,
> to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
> with: | example:
> subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> ----------------------------------------------------------------------------
> -
>
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the impatient,
> to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
> with: | example:
> subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
