On 16/03/06, MikeyG <[EMAIL PROTECTED]> wrote: > Hi, > Can anyone tell me how the ulimits specified in the default login.conf > are derrived? Is it worth changing them if I have one or two+ gigs of ram? > > I'd also like to force users to play nicer with each other in terms of > resources. Some are running things which spawn dozens of hungry > processes. However, it looks like most of these limits are on a per > process rather than per user basis (AFAICT; the man pages don't say a
The limits are on processes within that specific session group of processes, as far as I understand. > lot) and don't cause graceful degredation when they're reached. I'm > guessing these are really just a safety net to catch run-away processes. > Is there any better way to do this sort of thing? I usually play within the limits so I don't often run into them. How would you define graceful degradation when exceeding the alotted memory allocation limit or the limit for the number of processes? Is this (or, should this be) a feature of the OS, the shell, or of the process being limited. I have a feeling that if the process doesn't itself gracefully cope with limits, then there is not very much to be done... > > Thanks > MikeG > > Andreas -- Andreas Kahari
