On Wed, Nov 24, 2004 at 03:34:06PM +0000, Eric Andreychek wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Howdy, > > On Wed, 24 Nov 2004, Shailabh Nagar wrote: > > For the numtasks controller (which will do the fork bomb limiting you're > > looking for), 50% of available resources is still too many. > > If you see /rcfs/taskclass/stats, one of the cnt_* fields shows that > > 131072 tasks constitutes the "systemwide resource". > > Thanks for your response! I tried those steps out, and it didn't seem to > help. > That might be in the way I did something, so I'll explain how I did it. > > > Could you try the following: > > > > -Change the total_guarantee field in /rcfs/taskclass/shares to 131072 > > This part was straight forward: > > # echo "res=numtasks,total_guarantee=131072" > shares
you need to set max_limit also to 131072 for the class to make sure the child's limit is also absolute. With max_limit of 100 in the parent a 10 in class mean 10% of total resources of the parent, in your case it sould be 1310. Even in that case forks should have failed after creating 1310 preocesses. I don't see why it kept forking. can you try the above suggestion(setting max_limit also in the parent) and let us know the behavior. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
