On Nov 4, 2012, at 7:28 PM, Christopher Samuel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/11/12 09:05, Ralph Castain wrote:
>
>> System resource managers don't usually provide this capability, so
>> we will do it at the ORTE level.
>
> I would argue that the resource m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/11/12 01:43, Ralph Castain wrote:
> On Nov 4, 2012, at 7:28 PM, Christopher Samuel
> wrote:
>
>> I would argue that the resource managers *should* be doing it
>
> No argument from me - I would love for them to provide me with an
> easy API
On 11/5/12, Christopher Samuel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 06/11/12 01:43, Ralph Castain wrote:
>
>> On Nov 4, 2012, at 7:28 PM, Christopher Samuel
>> wrote:
>>
>>> I would argue that the resource managers *should* be doing it
>>
>> No argument from me - I woul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/11/12 13:01, Ralph Castain wrote:
> Depends on the use-case. If you are going to direct-launch the
> processes (e.g., using srun), then you are correct.
Yup.
> However, that isn't the case in other scenarios. For example, if
> you get an allo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/12 09:05, Ralph Castain wrote:
> System resource managers don't usually provide this capability, so we
> will do it at the ORTE level.
Interestingly one of the Torque developers posted this overnight:
http://www.supercluster.org/pipermail/t
