From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] protection against resource exhaustion
Date: Wed, 28 Jan 2015 17:02:52 +0000 [thread overview]
Message-ID: <CAJSxfm+3ub6_3SZBea-dLYZszUgSEeCtp5fQ9qibXA9g--JRiw@mail.gmail.com> (raw)
In-Reply-To: <7224032c68ae7df5d34def74c1245cbc@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
as someone mentioned, a dedicated real or virtual term (9vx, rpi+9pi) is
the right option. is there a reason this might not work for your
environment?
as for system watchdog, usually an external subsystem is used. i wonder if
a cpu (e.g. 9pi) dedicated to monitoring the main cpu's /proc (and perhaps
/net) for "abnormal activity" (whatever that is) and killing suspicious
procs could work.
On Wed Jan 28 2015 at 6:54:01 AM <lucio@proxima.alt.za> wrote:
> > the reason is that each process can have up to 16mb of stack, and this
> is unaccounted.
> > thus the stack or (seg)?brk can commit to memory that will fault when
> you touch it.
>
> It's a vague recollection, but the fact that the stack is being
> overcommitted rings a bell. Thanks, Erik.
>
> Lucio.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1037 bytes --]
next prev parent reply other threads:[~2015-01-28 17:02 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
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 [this message]
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=CAJSxfm+3ub6_3SZBea-dLYZszUgSEeCtp5fQ9qibXA9g--JRiw@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--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).