From: "Michael Oliver" <moliver@(email surpressed)>
Subject: job start time
   Date: Wed, 21 May 2008 17:45:32 -0400

Is there a way to submit a job to rush but tell it not to start until a 
later time?  The issue came up because an artist has a job that is going to 
take a while to render and does not want to hog the queue during the 
day...however they would like to submit the job now so it is ready to go 
later this evening. 

Why not use "WaitFor" on the submit script?  For example

waitfor 5:30pm
waitfor +04:15:00


On Wednesday 21 May 2008 15:03, Dylan Penhale wrote:
> Hi Michael
>
> Easiest way I can think, but bit of a bodge. Submit the job as normal, then
> pause it. Then set up a temporary cron job to unpause the job.
>
> Hacky but it would work. To my knowledge there isn't a clean way to apply a
> start time to a job.
>
> Dylan
>
> 2008/5/22 Michael Oliver <moliver@(email surpressed)>:
> > [posted to rush.general]
> >
> > Is there a way to submit a job to rush but tell it not to start until a
> > later time?  The issue came up because an artist has a job that is going
> > to take a while to render and does not want to hog the queue during the
> > day...however they would like to submit the job now so it is ready to go
> > later this evening.

Dylan Penhale wrote:
> Hi Michael
> 
> Easiest way I can think, but bit of a bodge. Submit the job as normal,
> then pause it. Then set up a temporary cron job to unpause the job.

	Or even easier, you can leave this running in a terminal:

rush -pause somejobid.123; sleep 3600; rush -cont somejobid.123

	..which would start the job in an hour.

	If you're on windows and don't have a 'sleep' command like unix,
	you can replace 'sleep 3600' with 'rush -sleep 3600' which does
	the same thing on all platforms.

> Hacky but it would work. To my knowledge there isn't a clean way to
> apply a start time to a job.

	'waitfor' is probably the best way, but I admit I sometimes like to use
	the above 'sleep' approach, just 'cause I'm such a command line freak.

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

Michael Oliver wrote:
> [posted to rush.general]
> 
> Is there a way to submit a job to rush but tell it not to start until a 
> later time?  The issue came up because an artist has a job that is going to 
> take a while to render and does not want to hog the queue during the 
> day...however they would like to submit the job now so it is ready to go 
> later this evening. 

	Yes, the 'waitfor' submit command allows several ways to specify
	a time to wait for before starting the job:
	http://www.seriss.com/rush-current/rush/rush-submit-cmds.html#WaitFor

	To use this in one of the GUI submit forms, you can specify the following
	at the 'Submit Commands:' prompt under the 'Rush' tab:

		waitfor 18:00

	..which will cause the job to remain in a 'wait' state until 6pm.

	Or, if you're using your own submit script, you can equally do:

rush -submit << EOF
..
waitfor 18:00
..
EOF

	Note that you can also specify relative times, eg.
	"waitfor +4h" for "4 hours from now", or a specific
	time and date. See the above link for examples.

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

I knew I had seen the time thing before but the help within the rush gui 
submit for shake only documents waiting for jobid's...... ;)
hahaha...anyways thanks everyone!

"Greg Ercolano" <erco@(email surpressed)> wrote in message 
news:1735-rush decimal general at seriss decimal com...
> Michael Oliver wrote:
>> [posted to rush.general]
>>
>> Is there a way to submit a job to rush but tell it not to start until a
>> later time?  The issue came up because an artist has a job that is going 
>> to
>> take a while to render and does not want to hog the queue during the
>> day...however they would like to submit the job now so it is ready to go
>> later this evening.
>
> Yes, the 'waitfor' submit command allows several ways to specify
> a time to wait for before starting the job:
> http://www.seriss.com/rush-current/rush/rush-submit-cmds.html#WaitFor
>
> To use this in one of the GUI submit forms, you can specify the following
> at the 'Submit Commands:' prompt under the 'Rush' tab:
>
> waitfor 18:00
>
> ..which will cause the job to remain in a 'wait' state until 6pm.
>
> Or, if you're using your own submit script, you can equally do:
>
> rush -submit << EOF
> .
> waitfor 18:00
> .
> EOF
>
> Note that you can also specify relative times, eg.
> "waitfor +4h" for "4 hours from now", or a specific
> time and date. See the above link for examples.
>
> -- 
> 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