[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] parsing the history file
- Date: Thu, 1 Mar 2012 12:24:55 +0000
- From: Thomas Luff <Thomas.Luff@xxxxxxx>
- Subject: Re: [Condor-users] parsing the history file
Well it really depends on what information you want from it
I use a perl wrapper that queries condor_history like so
condor_history -xml -constraint "ClusterId==714&&ProcId==0||ClusterId==720&&ProcId==0"
Then parse the xml output into an array of perl hashes, each representing a single job's classad.
Obviously sometimes the entire classad is too much but we use a number of attributes from it so it's easier than querying the specific attributes
From: condor-users-bounces@xxxxxxxxxxx [condor-users-bounces@xxxxxxxxxxx] On Behalf Of Rita [rmorgan466@xxxxxxxxx]
Sent: 01 March 2012 12:06
To: Condor-Users Mail List
Subject: [Condor-users] parsing the history file
I was wondering what is the best way to parse the condor history file? I suppose I can use condor_history -f filename -format ... but are there any alternatives? Has anyone built tools for such purposes?
--- Get your facts first, then you can distort them as you please.--
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.