[torquedev] job logging showjobs vmem patch

[Gareth.Williams at csiro.au]

I've just noticed that array jobs are not particularly well handled by the showjobs script:
wil240 at cheraxdev:~> showjobs -j 403[4]
wil240 at cheraxdev:~> showjobs -j 403[]
Unmatched [ in regex; marked by <-- HERE in m/^403[ <-- HERE ]\b/ at /usr/local/torque/bin/showjobs line 266, <JOBS> line 332

I'd be willing to work on a fix if no one else volunteers (and if anyone cares).

The log content seems fine and the following works:
showjobs 403

Gareth

> -----Original Message-----
> From: torquedev-bounces at supercluster.org [mailto:torquedev-
> bounces at supercluster.org] On Behalf Of Gareth.Williams at csiro.au
> Sent: Monday, 16 January 2012 2:19 PM
> To: torquedev at supercluster.org
> Subject: [ExternalEmail] [torquedev] job logging showjobs vmem patch
> 
> Hi Ken and David,
> 
> I've just started using the new job logging feature:
>  http://www.adaptivecomputing.com/resources/docs/torque/2-5-
> 9/10.1joblogging.php
> And found I needed to patch the showjobs script (from Adaptive) if I
> wanted it to report vmem usage.  Can you incorporate the patch please?
> Feel free to choose a better term than 'Vmemory Used'.
> 
> Regards,
> 
> Gareth
> 
> --- ./torque-3.0.4-snap.201201051014/contrib/showjobs   2010-12-07
> 09:44:20.000000000 +1100
> +++ /usr/local/torque/bin/showjobs      2012-01-16 13:58:43.000000000
> +1100
> @@ -182,6 +182,10 @@
>          {
>              $jobAttr{'Memory Used'} = $1;
>          }
> +        elsif ($line =~ /<vmem>([^<]+)</ && $context eq
> 'resources_used')
> +        {
> +            $jobAttr{'Vmemory Used'} = $1;
> +        }
>          elsif ($line =~ /<opsys>([^<]+)</ && $context eq
> 'resource_List')
>          {
>              $jobAttr{'Operating System'} = $1;
> @@ -317,6 +321,7 @@
>          'Wallclock Duration',
>          'CPUTime',
>          'Memory Used',
> +        'Vmemory Used',
>          'Submit Time',
>          'Start Time',
>          'End Time',
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev