|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
crontab job not running
Post 302280310 by vbe on Monday 26th of January 2009 12:59:53 PM
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have cornjob was scheduled at 1:00 AM everyday. It has been running fine since last Saturday. But it didn't run since Saturday. Because of daytime saving time change it didn't ran?
Please send me your thoughts.
Thanks in adavance.
Moe (3 Replies)
Discussion started by: Moe
3 Replies
2. 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
3. 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
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. Shell Programming and Scripting
Hi,
How to add a cron job in /etc/crontab using a shell script.??:confused:
Actually the requirement is we need to run a script say, XXX.sh every 10 min through “cron”.
That can be achieved by adding the below code line in the /etc/crontab , (i.e., “crontab -e ” command to add this to the... (4 Replies)
Discussion started by: Dedeepthi
4 Replies
6. 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
7. 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
8. Shell Programming and Scripting
I have put a cron entry in oracle user for taking hot backup every wednesday@ 2.30 AM and have given the cron entry
30 02 * * 3 /u01/vijay/hotbackupcron 2>&1 >> /u01/vijay/hotbackup.log
also find below the script inside hotbackupcron, i have put in env variables as well
... (13 Replies)
Discussion started by: vijaymec50
13 Replies
9. Shell Programming and Scripting
i have a job scheduled in crontab. The problem is, it is not running automatically as per the time scheduled. But runs when executed manually. What would be the problem? Help me with this please. (6 Replies)
Discussion started by: Santhosh CJ
6 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
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)