From: "Michael Oliver" <moliver@(email surpressed)>
Subject: command line submit and shake
   Date: Wed, 28 May 2008 16:23:50 -0400

I have a jobdone command running just fine.  It parses in the original shake 
file, grabs the rendered out images, throws them into another shake script, 
and then renders out a QT.  Problem is the process happens by the computer 
that submitted the original job.  (I know we could use a dedicated job 
server..and we probably should.. but that's not the current situation). 
Instead I would like to have the jobdone command submit a new job to rush 
and have it render on a designated computer (we'll call it qtRenderNode).

How do I go about using the command line to submit a new job in the 
background?  Is there an easy command line way or do I need to go back in 
and edit/re-parse the input file?
Been reading the newsgroups and reference manuals but also thought I'd go 
straight to the community.  Thanks in advance. 

Michael Oliver wrote:
> [posted to rush.general]
> 
> I have a jobdone command running just fine.  It parses in the original shake 
> file, grabs the rendered out images, throws them into another shake script, 
> and then renders out a QT.  Problem is the process happens by the computer 
> that submitted the original job.  (I know we could use a dedicated job 
> server..and we probably should.. but that's not the current situation). 
> Instead I would like to have the jobdone command submit a new job to rush 
> and have it render on a designated computer (we'll call it qtRenderNode).

	Right; you could have it 'rsh' the command to qtrendernode.

> How do I go about using the command line to submit a new job in the 
> background?  Is there an easy command line way or do I need to go back in 
> and edit/re-parse the input file?

	Yes, if you want to make your own submit script, there are
	some nice simple examples here in various languages (perl,python,csh,sh..):
	http://www.seriss.com/rush-current/rush/rush-submit.html

	Basically it comes down to piping some commands into 'rush -submit'.
	In your case it would be a 'one frame' job, so if you had a CSH
	script called "/yourserver/yourstuff/render-me.csh", you could
	submit it as a one frame job with:

rush -submit << EOF
title   YOURJOB
frames  1
command /yourserver/yourstuff/render-me.csh -arg1 -arg2
cpus    qtrendernode=1
EOF

	..where '-arg1' and '-arg2' are optional arguments to your script
	that eg. tells the script where to find the files to be converted,
	the quicktime filename to use, etc.

	And you can fire off the above from within your 'jobdonecommand'.
	Or, you can just make the jobdonecommand fire off rsh or ssh
	to run the quicktime conversion.



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

ny hints on getting rsh running?  I'm having a problems allowing rsh
connections to os x server. Response is :

server.domain.com:Connection refused
rsh: can't establish connection.

Any help would be greatly appreciated.  Thanks


"Greg Ercolano" <erco@(email surpressed)> wrote in message 
news:1747-rush decimal general at seriss decimal com...
> Michael Oliver wrote:
>> [posted to rush.general]
>>
>> I have a jobdone command running just fine.  It parses in the original 
>> shake
>> file, grabs the rendered out images, throws them into another shake 
>> script,
>> and then renders out a QT.  Problem is the process happens by the 
>> computer
>> that submitted the original job.  (I know we could use a dedicated job
>> server..and we probably should.. but that's not the current situation).
>> Instead I would like to have the jobdone command submit a new job to rush
>> and have it render on a designated computer (we'll call it qtRenderNode).
>
> Right; you could have it 'rsh' the command to qtrendernode.
>
>> How do I go about using the command line to submit a new job in the
>> background?  Is there an easy command line way or do I need to go back in
>> and edit/re-parse the input file?
>
> Yes, if you want to make your own submit script, there are
> some nice simple examples here in various languages 
> (perl,python,csh,sh..):
> http://www.seriss.com/rush-current/rush/rush-submit.html
>
> Basically it comes down to piping some commands into 'rush -submit'.
> In your case it would be a 'one frame' job, so if you had a CSH
> script called "/yourserver/yourstuff/render-me.csh", you could
> submit it as a one frame job with:
>
> rush -submit << EOF
> title   YOURJOB
> frames  1
> command /yourserver/yourstuff/render-me.csh -arg1 -arg2
> cpus    qtrendernode=1
> EOF
>
> ..where '-arg1' and '-arg2' are optional arguments to your script
> that eg. tells the script where to find the files to be converted,
> the quicktime filename to use, etc.
>
> And you can fire off the above from within your 'jobdonecommand'.
> Or, you can just make the jobdonecommand fire off rsh or ssh
> to run the quicktime conversion.
>
>
>
> -- 
> Greg Ercolano, erco@(email surpressed)
> Seriss Corporation
> Rush Render Queue, http://seriss.com/rush/
> Tel: 626-795-5922
> Fax: 626-795-5947
> Cel: 310-266-8906 

Michael Oliver wrote:

ny hints on getting rsh running?  I'm having a problems allowing rsh
connections to os x server. Response is :

server.domain.com:Connection refused
rsh: can't establish connection.

Any help would be greatly appreciated.  Thanks

    As root, you can turn rsh on this way:

service shell start
service login start

    (To turn it off, replace the 'start' with 'stop')

    From there it's a matter of the usual rsh configuration
    files, eg. ~/.rhosts and whatnot.

    For instance, to allow root to be able to rsh from
    machine to machine without it prompting for passwords,
    you might use:

echo + > /var/root/.rhosts
chmod 600 /var/root/.rhosts

    Pretty sure that's all that's necessary.

gotcha: http://www.seriss.com/rush-current/misc/rsh-config.html

Having an issue where windows boxes can not rsh to mac boxes.  Mac to Mac 
works great.
I get the following when trying to connect to a mac from a pc:

rsh host -l username uname
host: Permission denied.
rsh: can't establish connection

Firewalls have been disabled.

"greg ercolano" <erco@(email surpressed)> wrote in message 
news:1755-rush decimal general at seriss decimal com...
> Michael Oliver wrote:
>> ny hints on getting rsh running?  I'm having a problems allowing rsh
>> connections to os x server. Response is :
>>
>> server.domain.com:Connection refused
>> rsh: can't establish connection.
>>
>> Any help would be greatly appreciated.  Thanks
>
>     As root, you can turn rsh on this way:
>
> service shell start
> service login start
>
>     (To turn it off, replace the 'start' with 'stop')
>
>     From there it's a matter of the usual rsh configuration
>     files, eg. ~/.rhosts and whatnot.
>
>     For instance, to allow root to be able to rsh from
>     machine to machine without it prompting for passwords,
>     you might use:
>
> echo + > /var/root/.rhosts
> chmod 600 /var/root/.rhosts
>
>     Pretty sure that's all that's necessary. 

Michael Oliver wrote:

gotcha: http://www.seriss.com/rush-current/misc/rsh-config.html

	Ya, that works.

Having an issue where windows boxes can not rsh to mac boxes. Mac to Mac works great. I get the following when trying to connect to a mac from a pc:

rsh host -l username uname
host: Permission denied.
rsh: can't establish connection

	Sounds like a permission problem where the windows machine is
	logged in as a user that doesn't have an account on the mac,
	or that user doesn't have a 'wide open' .rhosts file.

	In my experience, window's client RSH is a little goofy
	in that it's not really interactive; when it runs a command,
	you don't see any output until the command is done.

	Should work though.. I have it working at my office.