From: Greg Ercolano <erco@(email surpressed)>
Subject: Rush FIFO fix
   Date: Wed, 29 Jul 2009 20:50:07 -0400

(If you don't use FIFO scheduling, you can ignore this)

The folks at Deluxe just helped me identify a problem with FIFO scheduling
when multiple job servers are in use.

We just nailed down the problem minutes ago, and I've found the problem
and I think I've fixed it.. will continue to do some testing, and should
have a fix release by tonight.

The problem shows up in Rush 102.42a9 thru 102.42a9b, and the problem
shows up where jobs simply don't always schedule in FIFO order when
multiple job servers are involved.

102.42a9c will have the fix.

You won't likely see the problem if all your jobs are being submitted
to a single job server (I know some of you prefer to run this way, so
you may not have noticed it). I suppose that is something of a "workaround"
if you don't have the ability to take the update.

Watch this space for release info.

Greg Ercolano wrote:
> (If you don't use FIFO scheduling, you can ignore this)
> 
> The folks at Deluxe just helped me identify a problem with FIFO scheduling
> when multiple job servers are in use.
> [..]
> Watch this space for release info.

	I've uploaded zip/tar files for Deluxe to try out; basically a new
	rushd daemon solves the problem.

	Once they've confirmed things are working well, I'll make the new
	fixes generally available.