From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: very long elapsed times in Frames report
   Date: Mon, 18 Sep 2006 03:01:13 -0400

Dylan Penhale wrote:

We have just noticed some very long elapsed times when using the frames report

e.g.

Fail 0116        2   snoopy          10728   spitfire.749     09/18,09:15:41     1191853:36:24
Fail 0125        1   hooch           29076   spitfire.749     09/18,09:21:44     1191853:30:15

This plays havoc with the max times settings. Any ideas where to start looking for this? All machines are time synced regularly.

	I'm pretty certain this is a windows specific problem.. I need to figure
	out the cause.

	Rush doesn't use normal time/date calls for the elapsed time calculations
	to avoid problems with changes in the date and time. eg. you can change
	the system clock's date and time without affecting the rush elapsed time
	indicators.

	Can you email me (directly) a zip'ed version of spitfire's
	rush/var/jobs-checkpoint file so I can see if I can trace this.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)