Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

at job executing before it's time?

Status
Not open for further replies.

Phyur

Technical User
Aug 28, 2001
3
JM
Greetings,

I have a job that I need to be executed at a later date relative to the execution time of another script. At the end of the 1st script I say &quot;at now + 3 hours < script > script.log&quot; and it seems as if at least one of the commands in the 2nd script is being executed immediately.

Can anybody shed some light on this situation?
 
This isn't going to answer your question, but it may be a work around: in your first script, why not issue a sleep command for 3 hours and then kick off the second script? For example:

<end of actions in the first script, as of now>
sleep 10800
/usr/local/bin/secondscript.sh
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top