10 More Discussions You Might Find Interesting
1. HP-UX
Hope you can help with a queuy i have. Server OS is HP-UX
my cron runs like this:
* * * * * /test/scripts/1_min_jobs.sh 1>/dev/null 2>/dev/null
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /test/scripts/jobs_5mins.sh 1>/dev/null 2>/dev/null
0,15,30,45 * * * *... (10 Replies)
Discussion started by: davexxash
10 Replies
2. Shell Programming and Scripting
Hi All,
Is there any way (any utility) to schedule a job to run once in a week on RedHat Linux ?
Note- Do not using Crontab.
Thanks
Pravin (1 Reply)
Discussion started by: pravin27
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Can anyone help me out with scheduling a cron job for the below:
i wnated to delete file from a folder on every sunday at 05:00 AM
this is code i have used.
*******************************************************
0 05 * * 0 find /abc/xyz/pqrs/bak/ -type f -mtime +30 -exec rm -f... (5 Replies)
Discussion started by: ch33ry
5 Replies
4. Shell Programming and Scripting
Hi all,
I am new to cron jobs..
i wanted to schedule a cron job that wil send a mail to me at 3:00PM on 10th August ie is on Wednesday.
0 15 10 8 3 echo "message from UNIX here"|mail -s "your subject here" user@user.com
However this was not executed...
Can anyone please... (0 Replies)
Discussion started by: ch33ry
0 Replies
5. Shell Programming and Scripting
Hi,
How to write the recursive function.
I have a script,
#!/usr/bin/ksh
##
name=$1
outputfile='output.log'
sqlplus -s > ${outputfile} <<__END__
${USER}/${PASS}@${DB}
WHENEVER SQLERROR EXIT SQL.SQLCODE ROLLBACK
WHENEVER OSERROR EXIT FAILURE ROLLBACK
SET ECHO ON
SET SERVEROUTPUT... (3 Replies)
Discussion started by: sandy1028
3 Replies
6. Solaris
Hi ,
I am trying to set up a cron job for getting the prstats for every 10 minutes to a log file.
prstat -s cpu -n 20 > a.txt
The issue is when i try to execute this command, a.txt is filling up with data for every second which is not i wanted.I just need top 20 processes for every 10... (2 Replies)
Discussion started by: pyaranoid
2 Replies
7. UNIX for Dummies Questions & Answers
I have cron scheduing that after hotbackup omniback kicks in and back up tape.
00 17 * * * /usr/local/bin/archbakPRD/mainPRDbackup.sh > /usr/local/bin/archbakPRD/dbfcopy.log 2 >&1
above cron can fired every night at 5PM but omnibackup need to have seperate name for each backup ( i.e:... (1 Reply)
Discussion started by: Paul.S
1 Replies
8. Shell Programming and Scripting
Hi,
from normal user(oracle) i am unable to run scheduled job in cron:
os version:
bash-2.03$ uname -a
SunOS sumail02 5.8 Generic_117350-39 sun4u sparc SUNW,Ultra-60
bash-2.03$ crontab -l
55 * * * * sh /oracle/statistics.sh > /dev/null 2>&1
bash-2.03$ cat /oracle/statistics.sh... (2 Replies)
Discussion started by: prakash.gr
2 Replies
9. Shell Programming and Scripting
the follwing script is running fine , when run from the ksh shell...it runs properly i.e. waits for a file "test.flag" and sends mail accordingly.
But when I schedule it in the crontab ...it does not run at the specified time (it never runs).
I am using ksh
####shell script starts
count=1... (4 Replies)
Discussion started by: ace@123
4 Replies
10. UNIX for Dummies Questions & Answers
HI,
I need to schedule a no.of jobs using the cron facility.
I currently do two kinds of scheduling,one based on the database load(after the database is loaded the program will start) and the other is based on time.....(say 10.00a.m daily)
the problem is..........
When the database is loaded... (1 Reply)
Discussion started by: sireesha15
1 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron 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).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD