Re: [gridengine users] write my own accounting log parser..

2011-05-08 Thread Dave Love
Stuart Barkley stua...@4gh.net writes: Yes, just roll the log file (see responses to your question on that). [Of course, qacct will only work for the entries left in `accounting' itself.] When you get to proper accounting, these details are very important. Being sure these edges don't

Re: [gridengine users] write my own accounting log parser..

2011-05-08 Thread Stuart Barkley
On Sun, 8 May 2011 at 09:58 -, Dave Love wrote: When you get to proper accounting, these details are very important. Being sure these edges don't duplicate or miss jobs and doing the desired processing for jobs splitting reporting boundaries is another Why don't the intermediate

Re: [gridengine users] write my own accounting log parser..

2011-05-08 Thread Dave Love
Stuart Barkley stua...@4gh.net writes: Why don't the intermediate accounting records cover that? Didn't know about them. Are they in the accounting file or just the reporting file? Sorry, just the latter. I don't remember what was in the original, but it's in

Re: [gridengine users] write my own accounting log parser..

2011-05-06 Thread Hung-ShengTsao (Lao Tsao) Ph.D.
On 5/6/2011 9:43 AM, Dave Love wrote: Hung-ShengTsao (Lao Tsao) Ph.D.laot...@gmail.com writes: may be you want to check this link https://twiki.grid.iu.edu/bin/view/Accounting/ Do you have experience of it? I vaguely remember looking at it and being put off, possibly because it was

Re: [gridengine users] write my own accounting log parser..

2011-05-06 Thread Reuti
Am 06.05.2011 um 19:17 schrieb Stuart Barkley: On Thu, 5 May 2011 at 16:46 -, William Deegan wrote: I'm pondering writing a python based dbwriter replacement which would just parse the accounting file and stuff it in a db, and then have some python web app framework for reporting.

Re: [gridengine users] write my own accounting log parser..

2011-05-05 Thread Chris Dagdigian
I've written perl scripts to scrape the accounting log and throw the entries into a mysql database - mainly so we could write our own simple queries and text based reporting tools. Never wrote the web app though at one time when I was entranced with ruby-on-rails I thought it would be a