9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] protection against resource exhaustion
Date: Sun, 25 Jan 2015 12:06:54 +0100	[thread overview]
Message-ID: <CAOCRf5XmiY0crB=bmC9G11TMu2kDFKDB5YqWvB9PWE7gqBR=_w@mail.gmail.com> (raw)
In-Reply-To: <4D3BDBE7-5023-4870-89E7-0A84C619941A@ar.aichi-u.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

>there must be a bug in rc.

Or maybe it does tail call elimination :)


2015-01-25 10:04 GMT+01:00 arisawa <arisawa@ar.aichi-u.ac.jp>:

> thank you, mischief.
>
> considering after I have posted previous mail,
> I have come to think that the script below should fail with error and stop
> execution.
>
> maia% cat foo
> #!/bin/rc
> ./foo
> maia%
>
> current rc does not stop execution.
> probably not due to protection problem by kernel.
> there must be a bug in rc.
>
> Kenji Arisawa
>
> > 2015/01/25 15:16、arisawa <arisawa@ar.aichi-u.ac.JP> のメール:
> >
> >
> > 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: 1601 bytes --]

      reply	other threads:[~2015-01-25 11:06 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
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 [this message]

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='CAOCRf5XmiY0crB=bmC9G11TMu2kDFKDB5YqWvB9PWE7gqBR=_w@mail.gmail.com' \
    --to=begnoc@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).