I see that the .common.pl is now stored with the submit scripts. OK. Now I'm would like to know if I can use my old .common.pl in the NEW location. Are they the same or did something change so that rather than replace the new with the old I need to instead merge them?

On Sep 26, 2005, at 1:40 PM, Gary Jaeger wrote:

actually, scratch that. I think I didn't follow the instructions here:

http://seriss.com/rush-current/submit-generic/mac-sysadmin-setup.html

properly. seems to work now. But another question. I'm a little unclear on how this is supposed to work:

foreach i ( host1 host2 host3 .. )
echo --- $i
rsh $i mv /usr/local/rush /usr/local/rush.pre-102.42
rcp -rp /usr/local/rush ${i}:/usr/local/rush
rsh $i /usr/local/rush/etc/bin/install.sh \; /usr/local/rush/etc/S99rush start
end

Am I supposed to run each of those individually? Sort of a novice here, but do I create a batch file and run that? This will probably sound really stupid, but how do I run all of that at once? I tried running just

rsh $i mv /usr/local ..

and got a connection refused so that's obviously a local problem, but any help for a non-sysadmin to do this?

On Sep 26, 2005, at 1:25 PM, Gary Jaeger wrote:

A couple questions about this. I'm starting to switch over to 102.42a from 102.41. I've got 102.42a installed on the license server (a pc) and one mac. I can ping and see the proper version on both machines. On the mac though, I can't run any of the submit scripts by double-clicking them. I can run

perl //CSSERVER/Apps2/rushscripts/submit-maya6.pl

and get the submit, but double-clicking seems to do nothing.

Another question. I'm a little unclear whether I'm supposed to have a .common.pl file in /usr/local/rush/etc if I want to use the new submits?

thanks

. . . . . . . . . . . . . . . . . . . . . . . .
Gary Jaeger // Core Studio
+ www.corestudio.com +

. . . . . . . . . . . . . . . . . . . . . . . .
Gary Jaeger // Core Studio
+ www.corestudio.com +

. . . . . . . . . . . . . . . . . . . . . . . .

Gary Jaeger // Core Studio

+ www.corestudio.com +

You can have both old and new submit scripts on the server, just keep them in separate dirs, ie: //yourserver/rushscripts-old/ //yourserver/rushscripts-new/ ..and users can use either or both with the new version of rush. Just keep the .common.pl files /separate/ for the old and new versions: o The old submit script's .common.pl file must live in /usr/local/rush/etc, and when changes are made to it, just copy it around with the the old 'rush -push .common.pl +any' technique. o The new submit script's .common.pl file will live on the file server in the same dir as the new submit scripts. To make changes to it, just edit that one copy on the server. No need to use 'rush -push'. Since the new version no longer has .common.pl in /usr/local/rush/etc, you can copy the /old one/ in there without fear of affecting the new scripts.

The .common.pl file changed quite a bit in the new release. I advise keeping the .common.pl files separate from one another, and maintaining them separately as above. Again: /usr/local/rush/etc/.common.pl -- .common.pl for old submit scripts //yourserver/rushscripts-new/.common.pl -- .common.pl for new submit scripts I don't really recommend trying to merge those files into one, though if you can if you really know what you're doing. The easiest thing is to just keep the files separate, and make changes separately as needed.

foreach i ( host1 host2 host3 .. ) echo --- $i rsh $i mv /usr/local/rush /usr/local/rush.pre-102.42 rcp -rp /usr/local/rush ${i}:/usr/local/rush rsh $i /usr/local/rush/etc/bin/install.sh \; /usr/local/rush/etc/S99rush start end

Actually, /those/ instructions are just for installing rush on new machines.. nothing to do with the submit scripts. You should only need to copy the new submit scripts to your file server /once/, then have all the users invoke the scripts from that directory, same as always. -- Greg Ercolano, erco@(email surpressed) Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed) Cel: (Tel# suppressed) Fax: (Tel# suppressed)