Hi Jesse, Thanks very much for your reply. See my inline comments below.
On Tue, May 10, 2016 at 1:37 PM, Jesse Connell <jess...@bu.edu> wrote: > Hi Mun, > > What's the shell set to for the queue? If I remember right csh is the > default (and it'll use the default if you don't specify -S). For example: > > For our setup "qconf -sconf | grep shell" shows: > > shell_start_mode posix_compliant > login_shells sh,bash,ksh,csh,tcsh > *[Mun] I get the same results. * > and "qconf -sq somequeue | grep shell" shows: > > shell /bin/bash > shell_start_mode posix_compliant > *[Mun] Yikes! Here are my results:* *shell /bin/csh* *shell_start_mode posix_compliant* *Okay, I'm new to grid config; so does the above imply that the CSH startup file will be automatically read (if found) for every qsub job?* > > We recently switched the shell from /bin/csh to /bin/bash on each queue > since so few were using csh anyway. This still tries to source > .bash_profile, since it'll be a login shell either way. (Is that the part > that's problematic, though, as opposed to csh vs. bash?) > *[Mun] Yes (if I understand correctly). That is, I don't want the shell startup file(s) to be read regardless of the configured shell for the queue. I want qsub to leverage the calling env's variables (thus, I use 'qsub -V'). Is that possible?* *Thanks again for the informative reply, Jesse.* *-- * *Mun* > Jesse > > > On 05/10/2016 01:30 PM, Mun Johl wrote: > >> Hi, >> >> I'm running OGS/GE 2011.11p1 on CentOS 6.5 . >> >> I have noticed that for some reason ~/.cshrc is read automatically for >> every qsub command I issue. My default environment is actually Bash; I >> only put a .cshrc in my home dir to test something for a peer and then I >> noticed qsub would read the .cshrc file automatically (which negatively >> affected my jobs). >> >> I do not have a .sge_request file in my home dir nor in the dir from >> where I launch qsub. And my qsub options do not include -S . >> >> I've tried various SGE DEBUG LEVELs, but none that I've tried have left >> breadcrumbs as to why ~/.cshrc was being read. >> >> This is driving me crazy, so any insight would be helpful. Yes, I >> _could_ just remove the .cshrc file, but others here actually use >> csh/tcsh and could be affected by this as well. Therefore, I'd like to >> root cause the issue if possible. >> >> Thanks, >> >> -- >> Mun >> >> >> >> _______________________________________________ >> users mailing list >> users@gridengine.org >> https://gridengine.org/mailman/listinfo/users >> >> _______________________________________________ > users mailing list > users@gridengine.org > https://gridengine.org/mailman/listinfo/users >
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
