Thanks for the clarification everyone.
Tim
On Monday 05 November 2007 05:41:00 pm Torsten Hoefler wrote:
> On Mon, Nov 05, 2007 at 05:32:04PM -0500, Brian W. Barrett wrote:
> > On Mon, 5 Nov 2007, Torsten Hoefler wrote:
> > > On Mon, Nov 05, 2007 at 04:57:19PM -0500, Brian W. Barrett wrote:
> > >
On Mon, Nov 05, 2007 at 05:32:04PM -0500, Brian W. Barrett wrote:
> On Mon, 5 Nov 2007, Torsten Hoefler wrote:
>
> > On Mon, Nov 05, 2007 at 04:57:19PM -0500, Brian W. Barrett wrote:
> >> This is extremely tricky to do. How do you know which environment
> >> variables to forward (foo in this case
> This is extremely tricky to do. How do you know which environment
> variables to forward (foo in this case) and which not to (hostname).
> SLURM has a better chance, since it's linux only and generally only run on
> tightly controlled clusters. But there's a whole variety of things that
> s
On Mon, 5 Nov 2007, Torsten Hoefler wrote:
On Mon, Nov 05, 2007 at 04:57:19PM -0500, Brian W. Barrett wrote:
This is extremely tricky to do. How do you know which environment
variables to forward (foo in this case) and which not to (hostname).
SLURM has a better chance, since it's linux only a
On Mon, Nov 05, 2007 at 04:57:19PM -0500, Brian W. Barrett wrote:
> This is extremely tricky to do. How do you know which environment
> variables to forward (foo in this case) and which not to (hostname).
> SLURM has a better chance, since it's linux only and generally only run on
> tightly con
This is extremely tricky to do. How do you know which environment
variables to forward (foo in this case) and which not to (hostname).
SLURM has a better chance, since it's linux only and generally only run on
tightly controlled clusters. But there's a whole variety of things that
shouldn't b
