Looks like a goof in documentation on our part -- the bhost(5) was
wrong. Sorry!
The correct attribute is "schedule", and the value you want is "no".
I'll ensure that bhost(5) is fixed for 7.1.2.
On Nov 12, 2004, at 12:14 PM, slaton wrote:
> hi Josh,
>
>> I am not very familiar with the "no-schedule" option in lamboot, but
>> the
>> user's guide uses "schedule=no". If the boot schema worked before,
>> then
>> that is probably not the problem.
>
> ah....I got "no-schedule" from the man page for bhosts (and from
> searching
> this last for "lam-bhost.def").
>
> i'll check out the schedule=no option for lamboot and see if that will
> work.
>
>> However, the user's guide states that even a "non-schedulable" node
>> can
>> be used in the mpirun command if it is explicitly stated (ie. nX, cX).
>> If you only want to perform a computation using 4 CPU's, then I would
>> explicitly select the machines to use, and put them in as arguments to
>> mpirun.
>
> actually, that was a simple example. the jobs are run on a cluster so
> it
> would not be convenient to have to specify every node each time a job
> is
> run.
>
> thanks for the reply,
> slaton
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
