From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] protection against resource exhaustion
Date: Tue, 27 Jan 2015 09:15:24 +0200 [thread overview]
Message-ID: <5e38f077840a332e8fd10fb77efa5a0b@proxima.alt.za> (raw)
In-Reply-To: <20150126231029.8c160c2541c3a8ed07c0a62f@eigenstate.org>
> IMO, instead of killing processes, it would be better to keep the hanging
> behavior in place, but place limits on the resources used by a subsection
> of the process tree. Think ulimit, but applying to entire process heirarchies.
Once you introduce limits, you become responsible for applying them
wisely. Good luck!
Lucio.
next prev parent reply other threads:[~2015-01-27 7:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 6:16 arisawa
2015-01-25 6:59 ` mischief
2015-01-25 17:41 ` erik quanstrom
2015-01-26 11:47 ` arisawa
2015-01-26 12:46 ` cinap_lenrek
2015-01-26 14:13 ` erik quanstrom
2015-01-27 0:33 ` arisawa
2015-01-27 1:30 ` Lyndon Nerenberg
2015-01-27 4:13 ` erik quanstrom
2015-01-27 4:22 ` erik quanstrom
2015-01-27 7:03 ` arisawa
2015-01-27 7:10 ` Ori Bernstein
2015-01-27 7:15 ` lucio [this message]
2015-01-27 14:05 ` erik quanstrom
2015-01-27 7:12 ` lucio
2015-01-27 14:10 ` erik quanstrom
2015-01-28 0:10 ` arisawa
2015-01-28 3:38 ` erik quanstrom
2015-01-28 6:50 ` arisawa
2015-01-28 7:22 ` lucio
2015-01-28 7:48 ` Quintile
2015-01-28 13:13 ` cinap_lenrek
2015-01-28 14:03 ` erik quanstrom
2015-01-28 14:09 ` lucio
2015-01-28 14:14 ` erik quanstrom
2015-01-28 14:53 ` lucio
2015-01-28 17:02 ` Skip Tavakkolian
2015-01-28 14:16 ` erik quanstrom
2015-01-28 17:28 ` Charles Forsyth
2015-01-28 17:39 ` cinap_lenrek
2015-01-28 18:51 ` Charles Forsyth
2015-01-29 3:57 ` arisawa
2015-01-29 6:34 ` erik quanstrom
2015-01-29 6:42 ` erik quanstrom
2015-01-29 8:11 ` arisawa
2015-01-27 10:53 ` Charles Forsyth
2015-01-27 14:01 ` erik quanstrom
2015-01-25 9:04 ` arisawa
2015-01-25 11:06 ` Bence Fábián
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=5e38f077840a332e8fd10fb77efa5a0b@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).