11-02-2005
Moe,
There has to be some other issue here, because the time change shouldn't affect cron jobs. I mean, maybe just maybe there could have been an issue Sunday morning where 2:00 AM would have gone back to 1:00 AM and so 1:00 AM would have occured twice that particular morning, but every day since should be just like before the change. What does this cron job do? Are you sure it's not being executed, or is it just not producing the results you are expecting?
Sully
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My cronjob triggers the script late by 6 minutes.
/var/cron/log shows that it got triggered at the right time then where can I track, the late starting of the script.
Is there some queue mechanism, some log?
This happens sometimes, not daily. but it affects me, whenever it happens.
Logging... (1 Reply)
Discussion started by: pksingh2
1 Replies
2. Shell Programming and Scripting
Hi,
i need to schedule a script to run at 6.10AM everyday.I tried to do this way.
#!bin/ksh
10 06 * * 0-6
sh /tmp/ss/script/daily_file_check.sh
And at the command prompt I did
>crontab -e cron.txt
I'm not sure whether this is the right way.
Can anyone please tell me how to... (4 Replies)
Discussion started by: kumarsaravana_s
4 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
down here part of the scheduled job in crontab (AIX Version 5)
i have problem running jspPRE-ALL.
i verrify permissions and privileges (the others job are working good)
if i run the job in command line it work correctly
#
# Aggiornamento doni e continuity
00 02 * * 2-6... (5 Replies)
Discussion started by: ilpasta
5 Replies
4. Shell Programming and Scripting
I would like to execute my script at 17.30 and 23.00 using crontab, could anybody help me out!!
Thanks in Advance!! (1 Reply)
Discussion started by: jatanig
1 Replies
5. AIX
Guys, yesterday i just make a script with email as a result and put them into crontab, it will execute on 23.33.
Today, i recieved email from system twice as result the script. the first email send at 23.02 and the second send at 23.33
how is the script execute two times ? the first job run... (6 Replies)
Discussion started by: michlix
6 Replies
6. Shell Programming and Scripting
Hi,
I am trying to execute a script (for once) during the booting time in Ubuntu system. However, the result is only showing the strings without without the variables.
Here is the script:
MgrIp=$(ec2-describe-instances --filter tag:Name=Mgr --filter instance-state-name=running | egrep... (4 Replies)
Discussion started by: turki_00
4 Replies
7. Shell Programming and Scripting
I am a newbie to Unix.
My default root user umask is set to 077 and I have the following crontab job to redirect al the backup output to the logfile of /backup/backup.xxxxx
00 10 * * 0 /usr/local/bin/backup.sh > /backup/backup.`date +\%Y\%m\%d` 2>&1
Since root default umask is 077, the... (2 Replies)
Discussion started by: famasutika
2 Replies
8. Shell Programming and Scripting
I have a ksh script that does the following
1. Script executes and creates an output file from a sql query
2. That output file is an input file to the script
3. generates an html file to email to DBA receipients
The following syntax works at the command line
... (1 Reply)
Discussion started by: JolietJake
1 Replies
9. SuSE
Hello,
This is my first posting in Linux world.
I have SLES 11.
I've created a file 'packdisk-scandisk.txt' file under /var/opt/Teradata/bteqdba.
The content of the file is,
cat /var/opt/Teradata/bteqdba/packdisk-scandisk.txt
output over /var/opt/Teradata/bteqdba/TAREAS_DBA.log... (2 Replies)
Discussion started by: JDBA
2 Replies
10. UNIX for Dummies Questions & Answers
hell all:
i am trying to test a crontab job for snmpwalk but it is not working:
here is crontab:
*/1 * * * * root /root/snmpwalk.sh
for the script, it is very simple:
#!/usr/local/bin/bash
/usr/local/bin/snmpwalk -v 2c -c public 100.10.10.10 (6 Replies)
Discussion started by: ipfreak
6 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable
in the crontab, if such exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO
crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)
AUTHORS
Paul Vixie <paul@vix.com>
BSD
June 17, 2007 BSD