On Fri, 2010-01-22 at 08:22 -0700, Ralph Castain wrote:
> A quick and easy way to answer my question of slurm vs ompi:
>
> Just do "srun script-that-echos-hostname-and-gethostname". If you get the
> right hostnames, then OMPI is to blame, not slurm.
>
No, I'm not...
Will check the configuration
On Jan 22 2010, Ralph Castain wrote:
For SLURM, there is a config file where you can specify what gets
propagated. It is clearly an error to include hostname as it messes many
things up, not just OMPI. Frankly, I've never seen someone do that on
SLURM.
Well, it's USUALLY an error That'
On Fri, 2010-01-22 at 08:12 -0700, Ralph Castain wrote:
> For SLURM, there is a config file where you can specify what gets propagated.
> It is clearly an error to include hostname as it messes many things up, not
> just OMPI. Frankly, I've never seen someone do that on SLURM.
>
I'm going to che
A quick and easy way to answer my question of slurm vs ompi:
Just do "srun script-that-echos-hostname-and-gethostname". If you get the right
hostnames, then OMPI is to blame, not slurm.
On Jan 22, 2010, at 8:07 AM, Ralph Castain wrote:
> Hi Nadia
>
> That sounds like a bug in your SLURM config
For SLURM, there is a config file where you can specify what gets propagated.
It is clearly an error to include hostname as it messes many things up, not
just OMPI. Frankly, I've never seen someone do that on SLURM.
I believe in this case OMPI is likely incorrectly picking up the environment
an
Hi Nadia
That sounds like a bug in your SLURM config file - SLURM certainly doesn't
propagate "hostname" by default as that would definitely mess things up for
more than OMPI.
Are you sure that SLURM is propagating the environment (something I have never
seen before)? Or is OMPI mistakenly pic
On Jan 22 2010, Nadia Derbey wrote:
I'm wondering whether the HOSTNAME environment variable shouldn't be
handled as a "special case" when the orted daemons launch the remote
jobs. This particularly applies to batch schedulers where the caller's
environment is copied to the remote job: we are inh
Hi,
I'm wondering whether the HOSTNAME environment variable shouldn't be
handled as a "special case" when the orted daemons launch the remote
jobs. This particularly applies to batch schedulers where the caller's
environment is copied to the remote job: we are inheriting a $HOSTNAME
which is the n
