[GE users] No job status, but process still runs

Pat Cable cable at ll.mit.edu
Tue Jul 10 18:53:17 BST 2007


    [ The following text is in the "windows-1252" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

Just FYI for anyone who might be searching,
    The GUI in Calibre 2007.2 works correctly, and makes the sun grid 
magic happen as it should.

// Patrick Cable II
// LLCad System Administrator Co-Op
// MIT Lincoln Laboratory - F-378
// 781 981 5996 - cable at ll.mit.edu



Daniel Templeton wrote:
> Something else to keep in mind is that Grid Engine sets an additional 
> group id for each job, so all children of that job will carry that 
> additional group id. (That's how Grid Engine accounts for usage of 
> children that end after the job itself.) You may be able to use that 
> to track the state of the forked children.
>
> I'd look to the process group (pgrp) as the first solution, though.
>
> Daniel
>
> Olesen, Mark wrote:
>>> I tried using the bash wait command but it's not capturing the PID. I
>>> also tried using fghack to no avail.
>>>
>>> Are there any resources I can look up on how to set up my wrapper
>>> script?
>>>     
>>
>> The preferred choice would be to get the software vendor to give you
>> information about how avoid forking or else implement this functionality
>> very soon.
>>
>> The only other possibility is brute force.
>> By inspection, try to see what PID/PGRP type of rules seem to be 
>> followed
>> when you start the process by hand (w/o GridEngine).
>> If there is just one of these jobs per machine/user, you could simply 
>> grep
>> the ps table for the appropriate PID.
>>
>> If the shell wait on pid gives you problems, you could also try a simple
>> Perl script with sleeping, querying the PID, etc.
>>
>> From perlfunc
>>     kill SIGNAL, LIST
>>     ...
>>     If SIGNAL is zero, no signal is sent to the process. This is a
>>     useful way to check that a child process is alive and hasn't
>>     changed its UID. See perlport for notes on the portability of
>>     this construct.
>>
>>
>> BTW: if you don't like having a separate Perl script, you can also 
>> use 'perl
>> -x' to embedded backing it into your shell script - see perlrun(1) for
>> details.
>>
>> good luck!
>>
>> /mark
>> This e-mail message and any attachments may contain legally 
>> privileged, confidential or proprietary Information, or information 
>> otherwise protected by law of EMCON Technologies, its affiliates, or 
>> third parties. This notice serves as marking of its ?Confidential? 
>> status as defined in any confidentiality agreements concerning the 
>> sender and recipient. If you are not the intended recipient(s), or 
>> the employee or agent responsible for delivery of this message to the 
>> intended recipient(s), you are hereby notified that any 
>> dissemination, distribution or copying of this e-mail message is 
>> strictly prohibited. If you have received this message in error, 
>> please immediately notify the sender and delete this e-mail message 
>> from your computer.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>>
>>   
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list