[torquedev] torque 4.1.2 login shells problem and bash -l workaround
chenry at ittc.ku.edu
Wed Oct 31 08:01:21 MDT 2012
Thanks, that is by far the simplest solution.
I was still trying to debug it yesterday. I think I'll stop trying and just use that solution, which is compatible with all my other torque configurations, managed through puppet.
----- Original Message -----
> From: "Christopher Samuel" <samuel at unimelb.edu.au>
> To: torquedev at supercluster.org
> Sent: Tuesday, October 30, 2012 10:32:46 PM
> Subject: Re: [torquedev] torque 4.1.2 login shells problem and bash -l workaround
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 19/10/12 05:34, Charles Henry wrote:
> > I have been following the torque 4 development, and I'm currently
> > using torque 4.1.2 on RHEL6.2. I have found that I cannot get
> > cluster jobs to run correctly without using "#!/bin/bash -l" in
> > each script.
> Just set:
> in /var/spool/torque/pbs_environment and that will force
> non-interactive bash to run /etc/profile on startup.
> In our environment we do:
> so only modules gets loaded, and then it's up to the users script to
> load the right modules for their job..
> - --
> Christopher Samuel Senior Systems Administrator
> VLSCI - Victorian Life Sciences Computation Initiative
> Email: samuel at unimelb.edu.au Phone: +61 (0)3 903 55545
> http://www.vlsci.org.au/ http://twitter.com/vlsci
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
> -----END PGP SIGNATURE-----
> torquedev mailing list
> torquedev at supercluster.org
More information about the torquedev