This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Am 31.01.2012 um 20:12 schrieb Jeff Squyres:
> I only noticed after the fact that Tom is also here at Cisco (it's a big company, after all :-) ).
> I've contacted him using our proprietary super-secret Cisco handshake (i.e., the internal phone network); I'll see if I can figure out the issues off-list.
But I would be interested in a statement about a hostlist for singleton startups. Or whether it's honoring the tight integration nodes more by accident than by design. And as said: I see a wrong allocation, as the initial ./Mpitest doesn't count as process. I get a 3+1 allocation instead of 2+2 (what is granted by SGE). If started with "mpiexec -np 1 ./Mpitest" all is fine.
> On Jan 31, 2012, at 1:08 PM, Dave Love wrote:
>> Reuti <reuti_at_[hidden]> writes:
>>> Maybe it's a side effect of a tight integration that it would start on
>>> the correct nodes (but I face an incorrect allocation of slots and an
>>> error message at the end if started without mpiexec), as in this case
>>> it has no command line option for the hostfile. How to get the
>>> requested nodes if started from the command line?
>> Yes, I wouldn't expect it to work without mpirun/mpiexec and, of course,
>> I basically agree with Reuti about the rest.
>> If there is an actual SGE problem or need for an enhancement, though,
>> please file it per https://arc.liv.ac.uk/trac/SGE#mail
>> users mailing list
> Jeff Squyres
> For corporate legal information go to:
> users mailing list