Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I don't necessarily agree. As I mentioned earlier, the constant which controls the number of processes per user is:/usr/src/linux/include/linux/tasks.h #define NR_TASKS 512 #define MAX_TASKS_PER_USER (NR_TASKS/2) #define MIN_TASKS_LEFT_FOR_ROOT 4 I verified this by changing 512 (which allowed me 244 tasks for a non-root user) to 768 which allowed over 380 processes, which was the expected number. I think what Mike was referring to is the number of open files. There is also a user and system wide limit here also. Again, most Unix systems have these limits built in to the kernel. On 22 Nov 98, at 5:17, Mike Bilow <mikebw at bilow.bilow.uu.ids.net> wrote: > Linux stores its process table as a chain of inodes, so you have to > increase the filesystem limits in the kernel source. You need to bump up > "NR_OPEN" in fs.h and in limits.h, and also bump up "OPEN_MAX" in > limits.h. The usual change is from 256 to 1024. Of course, you will need > to recompile. > +----------------------------------------------+ Gerald Feldman <gaf at mediaone.net> Boston Computer Solutions and Consulting ICQ#156300 *** Subcription/unsubscription/info requests: send e-mail with subject of "subscribe", "unsubscribe", or "info" to discuss-request at blu.org
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |