[padb-users] start using padb on TORQUE

[Jie Cai]

Thanks Ashley,

Yes, I have solved this problem via change group for "readlink".

Kind Regards,
Jie

-- 
Jie Cai                         Jie.Cai at anu.edu.au
ANU Supercomputer Facility      NCI National Facility
Leonard Huxley, Mills Road      Ph:  +61 2 6125 7965
Australian National University  Fax: +61 2 6125 8199
Canberra, ACT 0200, Australia   http://nf.nci.org.au
-----------------------------------------------------


On 27/11/10 07:39, Ashley Pittman wrote:
> Sorry about the last email, I clicked the wrong button!  See real response below.
>
> On 26 Nov 2010, at 02:45, Jie Cai wrote:
>    
>>>        
>> I found out that pid_to_name() does not pick the correct script process. I have following debug information:
>>
>> inner: x153: rmpid is 4376, name is lu.sh.
>> inner: x153: notscripts pid is 4376.
>>
>> I guess this is due to find_from_status() does not give the correct script name. I think it might be better to check /proc/$pid/cmdline to find the first element and to compare them with preset scripts keys.
>>      
> The lookup is done on the target of the "/proc/<pid>/exe" link if this is readable and only falls back to find_from_status() if it isn't (normally for SUID or other users processes) so if you have a shell script it should pick up /bin/sh which is then shortened to sh and looked up in the preset keys.  This is independent of the name of the wrapper script, I'd expect looking for ".sh" extensions on wrapper scripts to only catch a tiny minority of scripts which should all be caught by the previous mechanism anyway.
>
> It could be a permissions issue with the groups again that you are not able to read the destination of this sym-link and hence it's reverting back to the find_from_status() which doesn't to the indirection for interpreted languages?
>
> Ashley.
>
>