Dan Murray wrote:
I'm wondering if there's a way to restore the state of the queue prior
to the upgrade? That is, once the upgrade is done and a user starts
iRush, I'd like them to be able to see their old jobs.
It depends on what version you're upgrading from.
(Sometimes the file format of the caching files changes.)
The files to preserve would be everything in the rush/var
directory.
Assuming you preserve those files, you will probably be able
to resurrect the old jobs.
Do this on each machine you upgrade. You can just copy these
files over from the 'renamed away' version; copy them over
just before starting the daemon (ie. *after* running the install
script)
*Under Windows* be sure the permissions on these files (after you
copy them) are read/writable to all users, eg:
c:\rush\etc\bin\install.bat <-- first run the install script
copy \rush.old\var\* c:\rush\var <-- copy over the files
cacls c:\rush\var\* /e /c /g everyone:f <-- open the perms
net start rushd <-- start the daemon
If you have any trouble, please follow up here.
If this is dangerous or bad practice to try and do this, I'll accept
that but as stated, I'd prefer to restore the system state prior to the
upgrade.
I can say that it's for sure unsafe if you jump from 102.41 -> 102.42.
But if you're moving from 102.42a -> 102.42a8, its 'probably' fine.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|