From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: patch/list sorry/nbroken-8
Date: Thu, 30 Mar 2006 01:01:58 +0200 [thread overview]
Message-ID: <5f0780bda86d12586b41975a5458aa1e@cat-v.org> (raw)
In-Reply-To: <c9b8386f82b75be6378776d02fe355f5@cat-v.org>
>> d-rwxrwxr-x M 430 uriel sys 0 Mar 29 17:38 sorry/nbroken-8
>> from uriel@cat-v.org
>> /sys/src/9/port/proc.c
>> Upper NBROKEN to 8 to avoid lossing broken procs in long-running cpu servers.
>>
>> Wed Mar 29 17:37:57 EST 2006 rsc
>> This is an arbitrary choice. Why not 16?
>> If you want to make it different in your own systems go ahead,
Note also that keeping a customized version of the kernel source locally is
completely unacceptable.
uriel
next prev parent reply other threads:[~2006-03-29 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e644f5197ca0a9d59548f0fcf0c49f52@plan9.bell-labs.com>
2006-03-29 22:47 ` uriel
2006-03-29 22:57 ` Steve Simon
2006-03-29 23:01 ` uriel [this message]
2006-03-29 23:28 ` Skip Tavakkolian
2006-03-29 23:37 ` Russ Cox
2006-03-30 1:56 ` geoff
2006-03-30 10:52 ` Richard Miller
2006-03-30 12:15 Fco. J. Ballesteros
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=5f0780bda86d12586b41975a5458aa1e@cat-v.org \
--to=uriel@cat-v.org \
--cc=9fans@cse.psu.edu \
/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).