From: mischief@9.offblast.org
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
arisawa <arisawa@ar.aichi-u.ac.jp>
Subject: Re: [9fans] protection against resource exhaustion
Date: Sat, 24 Jan 2015 22:59:18 -0800 [thread overview]
Message-ID: <0F748B67-FB11-464C-84FA-66B4E0B29918@9.offblast.org> (raw)
In-Reply-To: <E9D002A0-CF5A-4059-96F9-9365F67D119B@ar.aichi-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
You would need to implement something like ulimits to fix process exhaustion, or some kind of rate limit. There are several forms of resource exhaustion in plan 9. One other that comes to mind is cat /dev/random prevents other clients from making progress reading /dev/random, such as cpu.
On January 24, 2015 10:16:32 PM PST, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>
>Hello 9fans
>
>my mac has a protection below:
>-bash$ cat foo
>#!/bin/sh
>./foo
>-bash$ ./foo
>./foo: fork: Resource temporarily unavailable
>-bash$
>
>on the other hand, Plan 9 does not.
>kernel is protected against such programs, however they are not killed.
>therefore no new process can be created.
>
>does anyone have idea to fix the problem?
>
>Kenji Arisawa
[-- Attachment #2: Type: text/html, Size: 1080 bytes --]
next prev parent reply other threads:[~2015-01-25 6:59 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 [this message]
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
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=0F748B67-FB11-464C-84FA-66B4E0B29918@9.offblast.org \
--to=mischief@9.offblast.org \
--cc=9fans@9fans.net \
--cc=arisawa@ar.aichi-u.ac.jp \
/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).