--- 2.3.1: - added 'stage' option to submit mode, which allows submission in a 'holding' state. thanks to Juan.Fernandez@eu.Takata.com for this fix! 2.3.0: - added ability to set state=holding - added holding to statuslister - ENV['RQ_JOB'] now has yaml dump of entire job when run - some minor mods to updater/deleter 2.2.0: - added start, stop, shutdown, and feeder modes - thanks to mikael borg for suggestion - improved query usage - added credits section to help 2.1.0: - enhanced status reporting - fixed bug where rotating failed due to prohibition of deletion of running jobs added in 2.0.0. the fixed basically adds a 'force' flag which is used by rotator.rb - made rotate a bit smarter: if a directory is given the rotation is automatically named and placed there. if a pathname is given the rotation is placed there, and if no pathname is given one is automatically generated. - made pidfile generation even more robust : a pidfile is only considered o.k. when the lock has been obtained AND the the pid (if any) found in the pidfile is not running. if a non-existent pid is found in the pidfile AND the lock could not be obtained it is assumed the nfslocking setup on that host is fubar and an auto-recovery takes place - fixed small bug which allowed the runner field of non-pending jobs to be updated 2.0.0: - deletion of running jobs is now prohibited (silently ignored actually). rq has no central process and no communication whatsoever is done between nodes. because of this it is not possible for delettion of a running job from the queue to somehow be signaled to the possibly remote node. however, it is NEVER an error to kill a job on some host - rq will simply report the failed exit_status - thus one can easily set up a simple command, perhaps using ssh keys, to kill a remote job and THEN delete it from the queue if this behaviour is truely needed. in simple terms a job may be removed from the queue BEFORE it starts running or AFTER is finishes -