[drmaa-wg] drmaa_wifsignaled() on Windows

[Peter Troeger]

> Does Condor installation install the Interix subsystem?  I do not  
> think
> it is a common service on Windows.

No, it does not. Condor Windows is a native Win32 application.

>
> The functionality could be needed in a mixed environment when the jobs
> are submitted thru DRMAA on Windows but run on Unix.

Exactly,  the crucial point is the type of execution host. When I  
submit a Unix binary from a Windows machine, the result of  
drmaa_wifsignaled() is useful even  on the Windows submission host.  
When I submit a Windows job from some operating system, then  
drmaa_wifsignaled() cannot provide any useful information, and I can  
only rely on the exit code of the job.

Regards,
Peter.


>
> Cheers
>
> 	Hrabri
>
>> -----Original Message-----
>> From: owner-drmaa-wg at ggf.org [mailto:owner-drmaa-wg at ggf.org] On  
>> Behalf
> Of
>> Peter Troeger
>> Sent: Thursday, January 26, 2006 1:47 PM
>> To: DRMAA Working Group
>> Subject: [drmaa-wg] drmaa_wifsignaled() on Windows
>>
>> Dear all,
>>
>> During the development of the Windows Condor DRMAA library, Greg
>> Quinn from the Condor team stumbled over the drmaa_wifsignaled()
>> function. Obviously, there is no well-defined meaning for this
>> function in native Windows applications.
>>
>> Windows supports the execution of POSIX applications with MS Services
>> for Unix (== Interix POSIX subsystem).
>> However, 99% of the Windows applications (including Windows Condor)
>> are native applications for the Win32 subsystem. Win32 relies on
>> structured exception handling as basic concept, instead of a signal-
>> based approach.
>>
>> SGE for Windows seems to solve the problem of a DRMAA library by
>> using the above mentioned SFU. Is this correct ?
>>
>> I propose to have this issue in the Condor DRMAA experience document,
>> as well as in the GridForge tracker.
>>
>> Regards,
>> Peter.