06-21-2011
Use this:
*/5 * * * <path>
If you really need for the command to run one minute after midnight, then every 5 minutes thereafter, you can include logic inside your "<path>" routine to ensure this, use the "sleep" command after checking the current minutes, perhaps with the date command: date +%M ... you might consider adding in a lock check too, if the sleep logic causes undesired overlap executions of the "<path>" routine.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Is there anyway to get the start time and end time / status of a crontab job which was just completed? Of course, we know the start time of the crontab job since we are scheduling. But I would like to know process start and time recorded somewhere or can be fetched from a command like 'ps'. ... (3 Replies)
Discussion started by: thambi
3 Replies
2. Shell Programming and Scripting
Hi,
I am a beginner in shell scripting but I have a task to complete where I have to extract the time of script execution in human format so anyone can run the script and understand what script is running when in simple format. Let me illustrate what I mean:
Two scripts in crontab, for this... (4 Replies)
Discussion started by: harjitsingh
4 Replies
3. Shell Programming and Scripting
hi,
what exaclt means the below in crontab
30 8-20/2 * * 1-5 /home/devtest/run.sh (1 Reply)
Discussion started by: mail2sant
1 Replies
4. Shell Programming and Scripting
im puting script in crontab, script is executing every 15min, every day, every monath
but i must make time range from 0:00 - 20:00 <> 20:30 - 0:00
or if i cant make 20:30 then 0:00 - 20:00 <> 21:00- 0:00
can i make it in single line like this?
7,22,37,52 0-23 * * * test.sh >/dev/null... (3 Replies)
Discussion started by: waso
3 Replies
5. Shell Programming and Scripting
Hi,
I want to set cron job for different time zone from my machine. So here is what I did to set it.
I am having a file cronfile, which I use to set cron jobs by using
Crontab cronfile
Now in cronfile I set TZ variable as
Set TZ=Asia/Calcutta
But now... (3 Replies)
Discussion started by: sarbjit
3 Replies
6. Solaris
I have set up my cron job on the solaris SunOS 5.10 Generic_138888-03 sun4u sparc SUNW,UltraAX-i2 but it is not running on time as expected.
Would you please help me to find out what I did wrong?
I want to have this cron job run once every month on the 1st Wednesday of the month, but it ran... (6 Replies)
Discussion started by: ggcc
6 Replies
7. AIX
This is a new one on me. We upgraded a system from AIX 5.3 TL 7 to 6.1 TL 7 yesterday. The app people notified us that their cron jobs weren't running at the right time. So I made a test cron entry and here's what I've found:
# crontab -l
* * * * * /usr/bin/date > /tmp/test.log 2>&1
# cat... (2 Replies)
Discussion started by: homeyjoe
2 Replies
8. Shell Programming and Scripting
Hello All,
I have created a shell script, When i run it manually as ./<script_name> it takes 5 hours to run, but when i am scheduling it in crontab, it is taking 20 hours to run.
Please help me and advice, what can be done to reduce the time in crontab.
Thank you (6 Replies)
Discussion started by: anand2308
6 Replies
9. UNIX for Advanced & Expert Users
Hello,
I am trying to run a script through crontab and it runs the first time and then it does not run.
I tried to run a simple script (as shown below) and I see the same issue.
#!/bin/ksh
clear
echo "Good Morning, World." > /tmp/test123
Crontab Entry:
30 09 * * *... (9 Replies)
Discussion started by: hasn318
9 Replies
10. Shell Programming and Scripting
I have crontab set to be triggered daily @ 8 am and 8:20 am server time.
00 08 * * * /web/scripts/check.sh
20 08 * * * /web/scripts/check.shuname -a
Linux mymac 3.10.0-327.36.3.el7.x86_64 #1 SMP Thu Oct 20 04:56:07 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
ls -ltr /web/scripts/check.sh... (9 Replies)
Discussion started by: mohtashims
9 Replies
LEARN ABOUT FREEBSD
sleep
SLEEP(1) BSD General Commands Manual SLEEP(1)
NAME
sleep -- suspend execution for an interval of time
SYNOPSIS
sleep seconds
DESCRIPTION
The sleep command suspends execution for a minimum of seconds.
If the sleep command receives a signal, it takes the standard action. When the SIGINFO signal is received, the estimate of the amount of
seconds left to sleep is printed on the standard output.
IMPLEMENTATION NOTES
The SIGALRM signal is not handled specially by this implementation.
The sleep command allows and honors a non-integer number of seconds to sleep in any form acceptable by strtod(3). This is a non-portable
extension, and its use will nearly guarantee that a shell script will not execute properly on another system.
EXIT STATUS
The sleep utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
To schedule the execution of a command for x number seconds later (with csh(1)):
(sleep 1800; sh command_file >& errors)&
This incantation would wait a half hour before running the script command_file. (See the at(1) utility.)
To reiteratively run a command (with the csh(1)):
while (1)
if (! -r zzz.rawdata) then
sleep 300
else
foreach i (`ls *.rawdata`)
sleep 70
awk -f collapse_data $i >> results
end
break
endif
end
The scenario for a script such as this might be: a program currently running is taking longer than expected to process a series of files, and
it would be nice to have another program start processing the files created by the first program as soon as it is finished (when zzz.rawdata
is created). The script checks every five minutes for the file zzz.rawdata, when the file is found, then another portion processing is done
courteously by sleeping for 70 seconds in between each awk job.
SEE ALSO
nanosleep(2), sleep(3)
STANDARDS
The sleep command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A sleep command appeared in Version 4 AT&T UNIX.
BSD
April 18, 1994 BSD