From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] killing processes
Date: Fri, 16 Sep 2005 10:53:43 +0900 [thread overview]
Message-ID: <5b58ed3b26b68a9a9751f6b79d306c10@orthanc.cc.titech.ac.jp> (raw)
> Ok, I'll ask this question which I've been meaning
> to look into: what is the easiest/cleanest way to
> restrict logins to our file server to certain people
> (to avoid, say, it running out of swap) while allowing
> everybody to log into our CPU server?
Split the authentication domain into two.
One for ordinary users in which "our CPU server" and
the file server (fossil processes) runs, and the other
in which the file server (the box itself) boots and runs.
my memo:
http://p9c.cc.titech.ac.jp/plan9/secp9.html#secventi
Hope this helps.
--
next reply other threads:[~2005-09-16 1:53 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 1:53 YAMANASHI Takeshi [this message]
2005-09-16 5:30 ` Dave Eckhardt
2005-09-16 5:41 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 15:52 Fco. J. Ballesteros
2005-09-15 15:38 Fco. J. Ballesteros
2005-09-15 15:46 ` Ronald G Minnich
2005-09-15 16:21 ` Lucio De Re
2005-09-15 16:41 ` Ronald G Minnich
2005-09-15 15:54 ` Lucio De Re
2005-09-15 15:04 Fco. J. Ballesteros
2005-09-15 15:19 ` Axel Belinfante
2005-09-15 17:06 ` andrey mirtchovski
2005-09-15 14:44 Fco. J. Ballesteros
2005-09-15 14:55 ` andrey mirtchovski
2005-09-15 15:02 ` Gabriel Diaz
2005-09-15 15:01 ` Axel Belinfante
2005-09-15 15:07 ` Uriel
2005-09-15 15:27 ` Russ Cox
2005-09-15 15:42 ` Lucio De Re
2005-09-15 15:50 ` Ronald G Minnich
2005-09-16 21:48 ` Wes Kussmaul
2005-09-17 0:48 ` Ronald G Minnich
2005-09-20 18:16 ` Steve Simon
2005-09-15 16:05 ` Uriel
2005-09-16 12:57 ` Axel Belinfante
2005-09-16 13:05 ` Lucio De Re
2005-09-16 13:21 ` Axel Belinfante
2005-09-16 13:42 ` andrey mirtchovski
2005-09-16 14:04 ` Sape Mullender
2005-09-16 14:20 ` Russ Cox
2005-09-17 6:28 ` Lucio De Re
2005-09-17 12:46 ` Sape Mullender
2005-09-17 15:07 ` Lucio De Re
2005-09-17 15:21 ` Russ Cox
2005-09-17 16:01 ` Lucio De Re
2005-09-18 13:02 ` Sape Mullender
2005-09-15 16:39 ` Charles Forsyth
2005-09-15 16:53 ` Ronald G Minnich
2005-09-15 20:27 ` Charles Forsyth
2005-09-16 3:09 ` Lyndon Nerenberg
2005-09-16 3:35 ` Ronald G Minnich
2005-09-15 15:32 ` Lucio De Re
2005-09-15 15:40 ` Ronald G Minnich
2005-09-15 15:49 ` jmk
2005-09-27 17:05 ` Ronald G Minnich
2005-09-15 16:00 ` Steve Simon
2005-09-16 2:17 ` Kenji Okamoto
2005-09-15 15:24 ` Lucio De Re
2005-09-15 15:44 ` Ronald G Minnich
2005-09-15 15:49 ` Brantley Coile
2005-09-15 19:13 ` Skip Tavakkolian
2005-09-15 14:18 Fco. J. Ballesteros
2005-09-15 14:35 ` Ronald G Minnich
2005-09-15 12:47 Fco. J. Ballesteros
2005-09-15 12:50 ` Charles Forsyth
2005-09-15 14:03 ` Ronald G Minnich
2005-09-15 17:31 ` ISHWAR RATTAN
2005-09-15 19:55 ` ISHWAR RATTAN
2005-09-15 20:09 ` Uriel
2005-09-15 18:28 ` Dave Eckhardt
2005-09-15 18:57 ` Russ Cox
2005-09-16 5:20 ` Dave Eckhardt
2005-09-16 6:40 ` Charles Forsyth
2005-09-16 13:34 ` erik quanstrom
2005-09-16 13:47 ` Uriel
2005-09-19 3:00 ` Bruce Ellis
2005-09-16 16:14 ` Dave Eckhardt
2005-09-15 11:48 ISHWAR RATTAN
2005-09-15 12:03 ` Steve Simon
2005-09-15 18:33 ` Enache Adrian
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=5b58ed3b26b68a9a9751f6b79d306c10@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.com \
--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).