From: Thunder from the hill <thunder@lightweight.ods.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jim Sibley <jlsibley@us.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Giuliano Pochini <pochini@shiny.it>, <riel@conectiva.com.br>
Subject: RE: Killing/balancing processes when overcommited
Date: Thu, 12 Sep 2002 14:43:58 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0209121441060.10048-100000@hawkeye.luckynet.adm> (raw)
In-Reply-To: <1031862920.2902.107.camel@irongate.swansea.linux.org.uk>
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
--
--./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
--/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
.- -/---/--/---/.-./.-./---/.--/.-.-.-
--./.-/-.../.-./.././.-../.-.-.-
next prev parent reply other threads:[~2002-09-12 20:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 19:00 Killing/balancing processes when overcommited Jim Sibley
2002-09-12 19:08 ` Thunder from the hill
2002-09-12 20:35 ` Alan Cox
2002-09-12 20:43 ` Thunder from the hill [this message]
2002-09-12 20:55 ` Alan Cox
2002-09-12 21:15 ` Thunder from the hill
2002-09-12 21:22 ` Jesse Pollard
2002-09-12 23:08 ` Alan Cox
2002-09-12 23:12 ` Thunder from the hill
2002-09-12 21:19 ` Jesse Pollard
2002-09-12 21:56 ` Thunder from the hill
2002-09-13 7:51 ` Giuliano Pochini
2002-09-13 10:17 ` Thunder from the hill
2002-09-12 19:09 ` Rik van Riel
2002-09-13 8:05 ` Giuliano Pochini
2002-09-13 10:54 ` Helge Hafting
2002-09-13 13:02 ` Giuliano Pochini
2002-09-13 16:40 ` Gerhard Mack
2002-09-13 20:23 ` Timothy D. Witham
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 21:13 Jim Sibley
2002-09-13 22:31 ` Timothy D. Witham
2002-09-13 22:38 ` Timothy D. Witham
2002-09-13 22:44 ` Rik van Riel
2002-09-13 23:12 ` Timothy D. Witham
2002-09-16 7:29 ` Helge Hafting
2002-09-16 14:03 ` Rik van Riel
2002-09-16 18:49 ` Timothy D. Witham
2002-09-16 19:11 ` Rik van Riel
2002-09-16 20:27 ` Timothy D. Witham
2002-09-14 0:23 ` Jim Sibley
2002-09-12 18:14 Jim Sibley
2002-09-11 18:08 Jim Sibley
2002-09-11 18:27 ` Jurriaan
2002-09-12 8:26 ` Helge Hafting
2002-09-11 21:44 ` Alan Cox
2002-09-12 7:06 ` Tim Connors
2002-09-12 7:25 ` Giuliano Pochini
2002-09-12 16:02 ` Rik van Riel
2002-09-12 18:30 ` Thunder from the hill
2002-09-13 8:17 ` Giuliano Pochini
2002-09-13 10:22 ` Thunder from the hill
2002-09-13 12:53 ` Denis Vlasenko
2002-09-13 12:54 ` Jesse Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0209121441060.10048-100000@hawkeye.luckynet.adm \
--to=thunder@lightweight.ods.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jlsibley@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@shiny.it \
--cc=riel@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).