On Mon, Feb 6, 2012 at 6:17 PM, Nate Coraor wrote:
>
> On Feb 6, 2012, at 1:05 PM, Nate Coraor wrote:
>
>>
>> On Feb 3, 2012, at 7:30 AM, Peter Cock wrote:
>>
>>> On Fri, Feb 3, 2012 at 11:55 AM, Ryan Golhar
>>> wrote:
'qstat -f | grep jobname' will give you the full jobname without
tr
On Feb 6, 2012, at 1:05 PM, Nate Coraor wrote:
>
> On Feb 3, 2012, at 7:30 AM, Peter Cock wrote:
>
>> On Fri, Feb 3, 2012 at 11:55 AM, Ryan Golhar
>> wrote:
>>> 'qstat -f | grep jobname' will give you the full jobname without truncation.
>>
>> Sadly not on our version of SGE - which appears t
On Feb 3, 2012, at 7:30 AM, Peter Cock wrote:
> On Fri, Feb 3, 2012 at 11:55 AM, Ryan Golhar
> wrote:
>> 'qstat -f | grep jobname' will give you the full jobname without truncation.
>
> Sadly not on our version of SGE - which appears to be SGE 6.2u5 - you
> get a bit more information but the jo
On Fri, Feb 3, 2012 at 11:55 AM, Ryan Golhar
wrote:
> 'qstat -f | grep jobname' will give you the full jobname without truncation.
Sadly not on our version of SGE - which appears to be SGE 6.2u5 - you
get a bit more information but the job name is still truncated as before.
> Personally, I thin
'qstat -f | grep jobname' will give you the full jobname without
truncation. Personally, I think the qstat reporting gives too little
information. I've written a perl script to parse the output of qstat -f to
give a bit more information. So truncation of jobnames for qstat shouldn't
be an issue.
Hello all,
We're not planning to try the new "run cluster jobs as user"
functionality (at least, not just yet), so for now all our SGE jobs
show on the cluster via qstat or any other monitoring tool as
belonging to the user "galaxy".
Currently the jobs are submitted as shell scripts "galaxy_NNN.s
