From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] How to reboot with normal user
Date: Wed, 20 Feb 2013 19:28:30 -0500 [thread overview]
Message-ID: <6b0716adb2cf7b262984d55c3798166d@coraid.com> (raw)
In-Reply-To: <CAPv5z_0hynL=ZFQ08r6sKrwmw-DQ1u1YirQ=KKs5hbzhpTO9-A@mail.gmail.com>
> How does one reboot remotely (from drawterm)?
> I see that /srv/fscons is chmod 600 and owned by bootes.
> What is the standard way to do this?
by cpuing in as bootes. from drawterm it is legal
to cpu -h $cpuserver -u bootes.
if you have more than a trivial number of machines,
a serial console server is a good idea. that makes this
sort of thing a little easier.
- erik
next prev parent reply other threads:[~2013-02-21 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 0:19 Costin Chirvasuta
2013-02-21 0:28 ` erik quanstrom [this message]
2013-02-21 0:45 ` Costin Chirvasuta
2013-02-21 0:47 ` Benjamin Huntsman
2013-02-21 0:51 ` erik quanstrom
2013-02-21 1:12 ` Benjamin Huntsman
2013-02-21 1:20 ` erik quanstrom
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=6b0716adb2cf7b262984d55c3798166d@coraid.com \
--to=quanstro@labs.coraid.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).