[1178] in athena10
Re: can a cluster machine be made ssh'able in?
daemon@ATHENA.MIT.EDU (Tim Abbott)
Thu Feb 19 14:44:18 2009
Date: Thu, 19 Feb 2009 14:44:03 -0500 (EST)
From: Tim Abbott <tabbott@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
cc: Alex T Prengel <alexp@mit.edu>, athena10@mit.edu
In-Reply-To: <1235072276.7373.35.camel@ray>
Message-ID: <alpine.DEB.2.00.0902191440480.21988@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
This is what we did on cluster-test.xvm.mit.edu:
# escape the chroot
chroot /proc/1/cwd/
# make sshd startable
rm /etc/ssh/sshd_not_to_be_run
# disable auto-reseting the cluster root; why does this exist anyway?
rm /etc/cron.daily/debathena-cluster-login-config
# set a root password that isn't the cluster root
passwd
and then reboot. This runs it outside the chroot and avoids running an
ssh server with a root password of the cluster root. It may be useful to
provide a new mechanism if we want to be able to create a new chroot from
the command line for debugging.
-Tim Abbott
On Thu, 19 Feb 2009, Greg Hudson wrote:
> Remove /etc/ssh/sshd_not_to_be_run and run /etc/init.d/ssh start.
>
> Upgrades to the debathena-cluster-login package will undo this change,
> so you may have to repeat it from time to time.
>
> (From an end-user perspective, debathena-cluster is only intended to be
> used by actual cluster machines. Obviously, machines used to test the
> debathena-cluster functionality are an exception.)
>
> On Thu, 2009-02-19 at 14:31 -0500, Alex T Prengel wrote:
> > Hi folks,
> >
> > As per subject- is there a way to configure a cluster Athena 10 machine so it
> > can be accessed remotely (presumably via ssh), while preserving its cluster
> > attributes including the chroot?
> >
> > It's a bit of a hassle having to run down the hall every time I need to
> > test or work on something, and I may need to check/test things from home
> > on occasion.
> >
> > Thanks,
> >
> > Alex
>
>
