[GE users] Usage of the tcsh-Shell instead the bash-Shell --> Problems
ChiefShadow at gmx.de
Tue Jan 3 08:49:25 GMT 2006
[ The following text is in the "iso-8859-1" character set. ]
[ Your display is set for the "ISO-8859-10" character set. ]
[ Some special characters may be displayed incorrectly. ]
> Von: Reuti <reuti at staff.uni-marburg.de>
> An: users at gridengine.sunsource.net
> Betreff: Re: [GE users] Usage of the tcsh-Shell instead the bash-Shell -->
> Datum: Mon, 2 Jan 2006 13:17:31 +0100
> The SGE_O_SHELL is just the shell used during submisision of the job,
> hence logged in with bash and then:
> reuti at login:~> chsh -s /bin/tcsh
> Changing login shell for reuti.
> Shell changed.
> reuti at login:~> qrsh "(source /usr/sge/default/common/settings.csh;
> qstat -j 6182)"
> sge_o_shell: /bin/bash
> it's still bash. And -S would only allow to change the shell for
> posix_compliant job scripts - won't help either for qrsh.
> I think, the only option would be to have the starting script for the
> Tight Integration to be generic in some way, or just convert it to tcsh.
What do you mean with generic, how should this work?
What function has qrsh, it is started in the rsh_wrapper, but how does it
work and which environment does qrsh use when it is started?
> -- Reuti
> Am 02.01.2006 um 10:28 schrieb Sebastian:
> > Hello,
> > of course we can change the shell, but this isn't a option.
> > Now i just implemented for each user the necessary options for the
> > bash-Shell and now i try to run the SGE under a bash-shell that all
> > will
> > work correct.
> > I set the -S option in the sge-batch-script, but the SGE_O_SHELL is
> > tcsh, i
> > think this variable is very important so how can i make this entry
> > right,
> > that it is bash?
> > Kind Regards, Sebastian
> >> --- Ursprüngliche Nachricht ---
> >> Von: Reuti <reuti at staff.uni-marburg.de>
> >> An: users at gridengine.sunsource.net
> >> Betreff: Re: [GE users] Usage of the tcsh-Shell instead the bash-
> >> Shell -->
> >> Problems
> >> Datum: Mon, 2 Jan 2006 09:43:28 +0100
> >> Hi,
> >> Am 02.01.2006 um 09:18 schrieb Sebastian:
> >>> Hello,
> >>> my SGE actually work for all bash-Shell-Users. But we have an LDAP-
> >>> Server
> >>> and there all User-Shells are fixed to the csh eg. the tcsh-Shell.
> >> depending on the LDAP setup, it might be possible to change the
> >> login shell there with:
> >> chsh
> >> simply from your login prompt, but this would of course mean to
> >> change it for all users (if they like this at all). (You have already
> >> unix_behavior in the queue definition, and mean the by qrsh started
> >> processes on the slave nodes I guess.)
> >> -- Reuti
> >>> Now i use the lam_tight_qrsh-Integration and some other scripts
> >>> which I run
> >>> beforce with the shell /bin/sh which links to bash.
> >>> Now is my question, must all script be written in the csh-syntax or
> >>> can i
> >>> make a little trick that the SGE uses the bash as here Environment
> >>> and that
> >>> all works fine like it does now.
> >>> Thanks,
> >>> Kind Regards,
> >>> Sebastian
DSL-Aktion wegen großer Nachfrage bis 28.2.2006 verlängert:
GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net
More information about the gridengine-users