Re: sge submit host question

From: Justin Riley <no email>
Date: Fri, 24 Feb 2012 16:36:03 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes the environment issue is related to the fact that SSH does not
source /etc/profile by default. For the time being you can get around
this using:

$ starcluster sshmaster mycluster 'source /etc/profile; <command>'

Sourcing /etc/profile should probably be done by default when running
commands using sshmaster/sshnode. I created an issue to keep track of
this:

http://web.mit.edu/star/cluster/issues/84

HTH,

~Justin


On 02/24/2012 03:38 PM, David Erickson wrote:
> On 2/24/2012 12:07 PM, Robert Yu wrote:
>> Hi,
>>
>> This is more of a best-practice question.
>>
>> Let's say I am on machine A. From it, I create a cluster. I can
>> then ssh into the "master" and launch jobs. Can this also be
>> done from machine A directly? I know one can do "starcluster
>> sshmaster -u sgeadmin<clustername> 'some command'" but then I
>> typically run into environment issues. Is there (simple) a way
>> to make machine A an sge submit host?
>>
>
> I ran into this too and found out I had to source
> /etc/profile.d/sge.sh. I also am curious if there is a better
> solution, presumably this is an interactive vs noninteractive shell
> issue.
>
> -D _______________________________________________ StarCluster
> mailing list StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9IAsIACgkQ4llAkMfDcrmLdQCbBH1KCzDASMcUx0smaFSWU9Gx
HY4An0QKuzBCpEi7ZCuQ06bY9LcRcPzw
=T/Lq
-----END PGP SIGNATURE-----
Received on Fri Feb 24 2012 - 16:36:06 EST