Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] condor_status bug?
- Date: Sun, 13 Jun 2010 09:32:48 -0400
- From: Matthew Farrellee <matt@xxxxxxxxxx>
- Subject: Re: [Condor-users] condor_status bug?
On 06/13/2010 12:27 AM, Burnett, Ben wrote:
> Hey:
>
> I can't recall if this is a know problem or not, but some googling for it did not return any meaningful results. It seems there is a slight problem with the argument handling in condor_status. The problem seems to revolve around the use of the -xml argument. Sometimes, depending on the where in the argument list the -xml option lies, condor_status thinks there is a conflict between it and some other argument condor_status has been given.
>
> For example, when using '-state' condor_status exhibits this behaviour:
>
> $ condor_status -xml -state
> Error: arg 2 (-state) contradicts arg 1 (-xml)
>
> Meanwhile, reversing the arguments works just fine:
>
> $ condor_status -state -xml
> <?xml version="1.0"?>
> <!DOCTYPE classads SYSTEM "classads.dtd">
> <classads>
> <c>
> <a n="MyType"><s>Machine</s></a>
> <a n="TargetType"><s>Job</s></a>
> ...
>
> The same is true for '-submitters', '-any', etc., but not for other arguments like '-attr', '-vm' or '-java'.
>
> Regards,
> -B
Sounds like a bug. You should search GT and file a ticket.
Best,
matt