Shell Programming and Scripting

Hi,
I am currently using the below at command, to schedule the script to run at a particular time,

at 2030 today <scriptname.ksh

I would like to know on how to run it every monday at around 11.30am (IST). Please help. Thanks in advance.

Hi yohasini,

you can try to set a cron job with this options:

Code:

30 20 * * 2 Script.sh # every monday at 20:30

30 11 * * 2 Script.sh # every monday at 11:30

Regards.

I had tried the cron job..it doesn't work..so had to go in with at..do u have any info on how to do it with AT command?

You can try something like:

Code:

at '11    utc+    30minutes' < Script.sh #To set the first run, assuming today is monday

or

at 1130 today  < Script.sh#To set the first run, assuming today is monday

or

at 11:30am  < Script.sh #To set the first run, assuming today is monday

And then go within the script and add at the end a line to invoke the Script.sh
itself to make a periodic task, something as follow:

Code:

at now +  next week < Script.sh

or 

at 1130 + 1 week < Script.sh
    
or
at 11:30am next week < Script.sh

Hope it helps.

Regards

at isn't meant for periodic scheduling, that's what cron is for. If it didn't work with cron, tell us the specific problem. Usually it's something along the lines of missing environment (cron doesn't read any of the profile scripts), missing path, incorrect assumptions about the working directory (cron will switch to a temporary path before executing your script).

The problem is i need to schedule a script to run on 16 servers and certain servers say that cron job doesn't exist,so we were asked to use at commands instead..

cron exists on (almost) all UNIX platforms, though a user may be excluded from using it. If that's the case (you'll get an appropriate error message when running crontab -e), ask your SA to enable that user.

The problem with using at is, simply put, that you can't be sure if your script is causing a problem. With at, you'll have to re-insert the script into the execution queue everytime it finishes, successful or not. As soon as the script is ended forcefully, either by user intervention or a system failure it's out of the loop, and you'd be resposible to re-enter it, while cron does this automatically.