9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to lock cpu console
Date: Wed,  1 Sep 2010 14:31:20 -0400	[thread overview]
Message-ID: <AANLkTik0rNKtGeFsecgxM9RJvADRa5s1461UU_8kbzjo@mail.gmail.com> (raw)
In-Reply-To: <c97bab42e8ecd634890713f8e8e88dd3@ladd.quanstro.net>

On Wed, Sep 1, 2010 at 2:14 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> rio is such a minor thing to run on today's massive machines, I'm not
>> sure I really see the problem in starting it on your cpu server
>> anyway. I frequently set them up to launch into rio because:
>> 1. It's easier to fix things when I can cat /dev/kprint in a window
>> rather than have it constantly interrupting me
>> 2. I like to be able to interrupt programs
>> 3. It's nice to run more than one thing at once, have a graphical editor, etc.
>> 4. Full-screen stats is pretty
>>
>> Of course, none of these reasons matter to you, since you don't run
>> rio on your servers AND you don't think there's any reason to lock
>> them (I agree!), I'm just pointing out that graphical lockers and rio
>> in general are far from useless on a cpu server.
>
> i'll buy that.  but i think you're missing the basic reason
> that the plan 9 cpu console is so minimal.  there's no
> reason to use one, unless you are doing the most basic of
> system maintence.  and using one is not without risk.
> for example
> - you've got admin privs.  it's easy to forget any abuse this.
> - an errant ^T^Tr ^P or vulcan nerve pinch reboots the
> server and not your terminal.
>
> here are some additional reasons that rio makes life
> more difficult
> - the serial console is now useless; no fixing or rebooting
> the machine from home
> - you need a kvm port or a real keyboard/video/mouse
> to fiddle with the machine even locally.
>
> for me, the loss of the serial console alone makes
> running rio on a cpu server a non starter.
> the serial console has saved me a good 3-4 trips into
> the office this year.
>
> - erik

Those are reasonable points, definitely. Since I'm usually the only
one to use my servers (except at Sandia, where I share with Ron),
abusing my admin privs isn't a big deal.

At Sandia, the cpu/auth/file server is connected to a serial
multiplexer, so I don't run rio there. At my university lab, I didn't
bother to connect a serial line or a KVM, but the server sits right
under my terminal, so I can swap the connectors around and get a
physical console if I really need one.

Sometimes there's a good reason to run rio, sometimes it's actively
counterproductive. Now that I've admitted there might be more one way
to do a thing, I should probably go put keyboard shortcuts into Acme
or something ;-)



John
-- 
"With MPI, familiarity breeds contempt. Contempt and nausea. Contempt,
nausea, and fear. Contempt, nausea, fear, and .." -- Ron Minnich



  reply	other threads:[~2010-09-01 18:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 14:20 baux80
2010-08-31 14:31 ` Robert Raschke
2010-08-31 14:55 ` John Floren
2010-08-31 15:04   ` erik quanstrom
2010-08-31 15:25     ` David Leimbach
2010-08-31 15:25     ` Skip Tavakkolian
2010-08-31 18:18       ` Francisco J Ballesteros
2010-08-31 19:54         ` andrey mirtchovski
2010-08-31 20:45       ` Skip Tavakkolian
2010-09-01  4:21         ` Federico G. Benavento
2010-09-01  4:44           ` John Floren
2010-09-01 15:11           ` erik quanstrom
2010-09-01 16:57             ` Federico G. Benavento
2010-09-01 17:22               ` erik quanstrom
2010-09-01 17:44                 ` John Floren
2010-09-01 18:14                   ` erik quanstrom
2010-09-01 18:31                     ` John Floren [this message]
2010-09-01 18:51                       ` erik quanstrom
2010-09-01 19:41                         ` John Floren
2010-09-01 18:24                   ` frank
2010-09-01 17:56                 ` Federico G. Benavento
2010-09-01 10:09         ` baux80 at gmail.com
2010-09-01 10:09         ` baux80
2010-09-01  9:56     ` baux80 at gmail.com
2010-09-01  9:56     ` baux80
     [not found]     ` <E1Oqk2g-0003Ze-1W@gouda.swtch.com>
2010-09-01 19:14       ` Corey
2010-09-01 19:52         ` erik quanstrom
2010-09-01 20:23           ` Corey
2010-09-01  9:48   ` baux80
2010-09-01  9:48   ` baux80 at gmail.com
     [not found] <E1OqRh3-0005IS-Hi@gouda.swtch.com>
2010-08-31 14:29 ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2010-08-31 14:20 baux80 at gmail.com

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=AANLkTik0rNKtGeFsecgxM9RJvADRa5s1461UU_8kbzjo@mail.gmail.com \
    --to=slawmaster@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).