Messages in this thread |  | | From | Jesse Pollard <> | Subject | Re: Killing/balancing processes when overcommited | Date | Thu, 12 Sep 2002 16:19:53 -0500 |
| |
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 Email: pollard@navo.hpc.mil
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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |