[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Fwd: Git Configuration
|
Hi Claudia,
It would be much easier if we could do this, but some systems (e.g. AIX) don't have bash installed.
What problem are you having with the build? The remote builder should just be running 'ssh user@system make all'.
Greg
On Dec 8, 2011, at 10:14 AM, Claudia Knobloch wrote:
> Hi all,
>
> in the last days I had a lively discussion with one of our BlueGene/P admins. Here is one of his suggestions:
>
> Why not using
>
> ssh user@system "bash -lc '<cmd>'"
>
> or
>
> ssh user@system "bash -ic '<cmd>'"
>
> instead of
>
> ssh user@system "<cmd>"
>
> in that case you have the same environment as if the user logs in directly. And one has full control over this environment with .profile/.bashrc without involving a sysadmin. And you also get rid of the problems with different login shells as long as bash is installed on the system.
> This might also make debugging easier because there is no difference between starting a command through PTP and doing the same directly logged in.
>
>
> BTW, he is also interested in how PTP is talking withe the SSH demon on the remote side during building since we are still not able to build the code on our BlueGene.
>
> Kind regards,
> Claudia
>
> On 12/07/11 01:12, Roland Schulz wrote:
>>
>>
>> On Tue, Dec 6, 2011 at 9:53 AM, Alameda, Jay<alameda@xxxxxxxxxxxx<mailto:alameda@xxxxxxxxxxxx>> wrote:
>> Roland, Beth, Claudia,
>>
>> You touched on something that has really make life difficult – the “on some machines one cannot set the environment” – (which leads to the .ssh trick that was discussed on this list). Do you know how the machine is set so that the BASH environment cannot be set (and more importantly, how to fix it?) we have some systems in XSEDE with this characteristic, which makes them really difficult to use. Looking for clues ….
>>
>> The system admin has to set BASH_ENV. I don't know how the system admin has to do that. In theory, SSH allows the user to set it, but only if AcceptEnv or PermitUserEnvironment is enabled for the ssh server. And this is usually not the case. So all the user can usually do, is to ask the system admin to set BASH_ENV.
>>
>> We probably should have an option to set environment variables in the RemoteConfiguration dialog (the one to create/edit RemoteTools connections). Independent of this it is probably a good idea to be able to have task specific ways to set the environment (e.g. for Sync the Git path or for buiild the compiler using e.g. modules). But if it would be possible to set enviroment in the RemoteConfiguration dialog one could set the remote environment independent of the task and would have a fall back if the specific task doesn't have an option to set the environment.
>>
>> Roland
>>
>> Thanks,
>>
>> Jay
>>
>>
>> From: ptp-dev-bounces@xxxxxxxxxxx<mailto:ptp-dev-bounces@xxxxxxxxxxx> [mailto:ptp-dev-bounces@xxxxxxxxxxx<mailto:ptp-dev-bounces@xxxxxxxxxxx>] On Behalf Of Beth Tibbitts
>> Sent: Monday, December 05, 2011 10:00 PM
>>
>> To: Parallel Tools Platform general developers
>> Subject: Re: [ptp-dev] Fwd: Git Configuration
>>
>>
>> Thanks guys. You answered some of the questions I had about how and why this works the way it does.
>>
>> FWIW for the PTP tutorial on the NCSA forge machine, it used tcsh (in the training IDs we set up ) and we got that to work; like Corey I usually would rather use bash.
>> I updated the FAQ page with some of your remarks.
>>
>> ...Beth
>>
>> Beth Tibbitts
>> Eclipse Parallel Tools Platform http://eclipse.org/ptp
>> IBM STG - High Performance Computing Tools
>> Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
>>
>> Roland Schulz ---12/05/2011 08:02:44 PM---Hi, When non-interactive shells are launched BASH_ENV is read. If BASH_ENV is not set on your system
>> From:
>>
>>
>> Roland Schulz<roland@xxxxxxx<mailto:roland@xxxxxxx>>
>>
>> To:
>>
>>
>> Parallel Tools Platform general developers<ptp-dev@xxxxxxxxxxx<mailto:ptp-dev@xxxxxxxxxxx>>,
>>
>> Date:
>>
>>
>> 12/05/2011 08:02 PM
>>
>> Subject:
>>
>>
>> Re: [ptp-dev] Fwd: Git Configuration (ENVIRONMENT)
>>
>> Sent by:
>>
>>
>> ptp-dev-bounces@xxxxxxxxxxx<mailto:ptp-dev-bounces@xxxxxxxxxxx>
>>
>> ________________________________
>>
>>
>>
>> Hi,
>>
>> When non-interactive shells are launched BASH_ENV is read. If BASH_ENV is not set on your system than it is not possible to set any environment variables. Bash reads for interactive shells ( ~/.bash_profile, ~/.bash_login, or ~/.profile for login shells and ~/.bashrc for non-login shells). But for non-interactive shells it does not have any default and it depends on the system configuration. Most systems, I have access to, have it configured to read ~/.bashrc. But not all; and on those I cannot can set the environment.
>>
>> Roland
>>
>> On Mon, Dec 5, 2011 at 7:07 AM, Beth Tibbitts<tibbitts@xxxxxxxxxx<mailto:tibbitts@xxxxxxxxxx>> wrote:
>> Claudia
>> See http://wiki.eclipse.org/PTP/FAQ#Q:_My_remote_or_synchronized_project_doesn.27t_find_the_remote_environment_variables_correctly
>> You need to make sure that a non-interactive shell gets the right environment setup.
>> Altho, based on my expericence, .bashrc is the one it calls.
>> Interactive shells can call .profile or .bash_profile (need to update that wiki page)
>>
>> ...Beth
>>
>> Beth Tibbitts
>> Eclipse Parallel Tools Platform http://eclipse.org/ptp
>> IBM STG - High Performance Computing Tools
>> Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
>>
>> Claudia Knobloch ---12/05/2011 05:24:39 AM---Hi, we run into a little problem here in Jülich. One of our users tried out
>>
>> From:
>>
>>
>> Claudia Knobloch<c.knobloch@xxxxxxxxxxxxx<mailto:c.knobloch@xxxxxxxxxxxxx>>
>>
>> To:
>>
>>
>> <ptp-dev@xxxxxxxxxxx<mailto:ptp-dev@xxxxxxxxxxx>>,
>>
>> Date:
>>
>>
>> 12/05/2011 05:24 AM
>>
>> Subject:
>>
>>
>> [ptp-dev] Fwd: Git Configuration
>>
>> Sent by:
>>
>>
>> ptp-dev-bounces@xxxxxxxxxxx<mailto:ptp-dev-bounces@xxxxxxxxxxx>
>>
>> ________________________________
>>
>>
>>
>>
>> Hi,
>>
>> we run into a little problem here in Jülich. One of our users tried out
>> the feature synchronized projects and could not synchronized his project
>> with the system Jugene.
>>
>> Git is installed on Jugene, but not automatically loaded. I put the
>> module load command into the .bashrc, but the command
>>
>> ssh user@jugene [command]
>>
>> does not load the .bashrc file. Is it possible to configure the path of
>> git, like
>>
>> ssh user@jugene /usr/.../git?
>>
>> Kind regards,
>> Claudia Knobloch
>>
>> ------------------------------------------------------------------------------------------------
>> ------------------------------------------------------------------------------------------------
>> Forschungszentrum Juelich GmbH
>> 52425 Juelich
>> Sitz der Gesellschaft: Juelich
>> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
>> Vorsitzender des Aufsichtsrats: MinDirig Dr. Karl Eugen Huthmacher
>> Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
>> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
>> Prof. Dr. Sebastian M. Schmidt
>> ------------------------------------------------------------------------------------------------
>> ------------------------------------------------------------------------------------------------
>> _______________________________________________
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx<mailto:ptp-dev@xxxxxxxxxxx>
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>
>>
>>
>>
>> --
>> ORNL/UT Center for Molecular Biophysics cmb.ornl.gov<http://cmb.ornl.gov/>
>> 865-241-1537<tel:865-241-1537>, ORNL PO BOX 2008 MS6309_______________________________________________
>>
>> ptp-dev mailing list
>> ptp-dev@xxxxxxxxxxx<mailto:ptp-dev@xxxxxxxxxxx>
>> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>>
>>
>>
>>
>> --
>> ORNL/UT Center for Molecular Biophysics cmb.ornl.gov<http://cmb.ornl.gov>
>> 865-241-1537<tel:865-241-1537>, ORNL PO BOX 2008 MS6309
>>
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
