[1179] in athena10
Re: can a cluster machine be made ssh'able in?
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Feb 19 14:44:58 2009
Cc: Alex T Prengel <alexp@mit.edu>, athena10@mit.edu
Message-Id: <CB840EC9-CA92-42A7-86AA-3BE97EBE5F9E@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
In-Reply-To: <1235072276.7373.35.camel@ray>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Thu, 19 Feb 2009 14:43:20 -0500
Except that if you ssh in this way, you end up outside the chroot, and
that makes it not very useful for testing. (For example, the MATLAB
and Mathematica problems would not have manifested themselves in such
an environment)
Alex and I talked about this earlier, and it seems like the only
options are VMware or VNC if you want to test something exactly as in
a cluster environment, correct?
-Jon
On Feb 19, 2009, at 2:37 PM, 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
>
