Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am looking for some assistance with Linux process limits.
When working in our computer lab on Operating Systems course assignments, students often write bad C programs that time up our time sharing systems -- the sort of "while(1) fork" equivalents. As a result, we added a process limit of 1024 processes to our system by modifying the /etc/security/limits.conf file. We tested that the the limit worked with our own forking program, and everything worked just fine. We were able to run a user up to his process limit. Any future attempts to login through any means of logging into our system for that user would not work. If the user had other windows already open on the system and tried to execute other commands, he would see "out of procesess". Today, we noticed that one student was running a forking program, and had over 7000 processes occupied. We do not understand how this program could get around the process limit. He certainly wasn't trying to get around the limit. Maybe someone could offer some feedback.. We are running a Linux 2.4.26 kernel.
In the process table, all of the processes looked like this:
040 D <u> 27811 1 0 69 0 - 359 down 09:45 ? 00:00:00 a.out
240 S <u> 3911 1 0 69 0 - 359 end 09:47 ? 00:00:00 a.out
040 S <u> 13205 12417 0 69 0 - 357 nanosl 09:48 ? 00:00:00 a.out
040 S <u> 14555 14346 0 73 0 - 357 wait4 09:48 ? 00:00:00 a.out
I would understand if all but 1024 of them were defunct/zombies but that's not the case.
Can anyone shed any light on what I might be missing?
I was using just "ps -elf". Unfortunately I can't change the tags because what you see is the output that I captured from the
screen. We had to kill all the processes off to get our system back to normal again.