Hi, Below are the some points which U can try out.
1. vi /proc/sys/fs/file-max :--> Increase this parameter by calcuating RAM. I mean if U have 128 MB RAM, as for every 256 it takes 4mb. so for 128/4=32, which again 256*32=8192 2. echo "32768 61000" > /proc/sys/net/ipv4/ip_local_port_range. where 32768, which is TCP, this increase the PORT RANGE. And other is 61000 which increase the UDP port range. 3. chattr +A FileName / chattr -R +A <directory>.--- > when ever some one accessing the files, unix records the time. which i feel comsumes processing Jai -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Keller Sent: Thursday, October 04, 2001 12:35 AM To: [EMAIL PROTECTED] Subject: Re: Max number of processes On Wed, 2001-10-03 at 11:19, Matthias Saou wrote: > Once upon a time, Matthias Saou <[EMAIL PROTECTED]> wrote : > > > Hi, > > > > I'm having a bit of trouble on some loaded web servers. Having > recompiled > > apache after raising it's upper possible limit of processes, once it > > reaches a bit more than 400 processes, my shell goes berzerk, forks are > > impossible... a real mess. > > OK, after searching a bit more, I've found it. I'm running a 2.2.19 > kernel, so here is the problem : > > #define NR_TASKS 512 /* On x86 Max about 4000 */ > > (from /usr/src/linux-2.2.19/include/linux/tasks.h) > > This is a fairly low limit IMHO... now let's recompile that kernel! > Just a couple of questions. Are NR_TASKS == unix processes? According to your first message you were topping out around 400. The kernel would be configured for 4000 according to the tasks.h entry? Sounds like a lot of growing room. -- Christopher Keller Systems Engineer BeamReach Networks -- Sunnyvale, CA _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
