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)
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)
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)
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)
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)
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)
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)
Scheduled job is not running on time.but it is running when executing same command manually.
25 10 * * * /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Manually executing the same
Ksh -x /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Followed steps
Crontab -e
Added the job to cron tab. (4 Replies)
Discussion started by: Myguest
4 Replies
LEARN ABOUT OPENSOLARIS
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1 A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.11 1 Mar 1994 queuedefs(4)
09-09-2013
)