[lkml]   [2002]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Killing/balancing processes when overcommited
On Thursday 12 September 2002 03:43 pm, Thunder from the hill wrote:
> Hi,
> On 12 Sep 2002, Alan Cox wrote:
> > On Thu, 2002-09-12 at 20:08, Thunder from the hill wrote:
> > > These problems can be solved via ulimit. I was referring to things
> > > like rsyncd which was blowing up under certain situations, but runs
> > > under a trusted account (say UID=0). In order to condemn it you'd need
> > > the setup I've mentioned.
> >
> > Ulimit won't help you one iota
> Why so pessimistic? You can ban users using ulimit, as you know. (You will
> always remember when you wake up and your memory is ulimited to 1MB.)
> Thunder

ulimit is a per login limit, not a global per user limit. The sum of all user
logins can still exceed the available memory. Even a large number of
simultaneous network connections (telnetd/sshd) can drive a system OOM.

Now, which of these processes should be killed?
Jesse I Pollard, II

Any opinions expressed are solely my own.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.086 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site