03-09-2012
Update:
We found the problem is with the TZ variable in /etc/environment.
We still had last years dates in it:
TZ=CST6CDT,M3.2.0/2:00:00,M11.1.0/2:00:00
We changed it to:
TZ=CST6CDT,M3.11.0/2:00:00,M11.4.0/2:00:00
Then restarted cron and now life is good.
This User Gave Thanks to homeyjoe For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Can some one help me getting last hour of the current time with date command in a script. (7 Replies)
Discussion started by: shehzad_m
7 Replies
2. Shell Programming and Scripting
Hi,
I need to get the date and time for past 1 hour from the current date. Anyone know how to do so?
Thanks (5 Replies)
Discussion started by: spch2o
5 Replies
3. Shell Programming and Scripting
Hello,
I've created the script below to compare the content of two files with a delay of an hour. After an hour, the lines that exist in both files, will be printed and executed.
The script now uses a counter to countdown 50 minutes. But what I would prefer is to check the file timestamp of... (3 Replies)
Discussion started by: taipan
3 Replies
4. Shell Programming and Scripting
How to set crontab for every minute or every hour (1 Reply)
Discussion started by: kaushik02018
1 Replies
5. UNIX for Dummies Questions & Answers
I want to add a crontab entry which should execute for every 4 hours and that 4 hours calculation should begin from the current time.
Normally if I set the crontab entry like this,
00 */4 30 05 * root date >>/tmp/cronout
The above will execute the date command for every 4 hours like... (7 Replies)
Discussion started by: Ganeshwari
7 Replies
6. Shell Programming and Scripting
Hi,
Can anyone help me in finding how to run a specific job every hour without using crontab.
Say for example i need to run a command ps -aux in the starting of every hour.. (3 Replies)
Discussion started by: glv
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
When I set the crontab to run every minute, every hour, it works fine.
* * * * * env > /tmp/env.output
However I want to run it every day at 8:00 AM and it does not run.
* 8 * * * env > /tmp/env.output
I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (5 Replies)
Discussion started by: samantha13
5 Replies
8. Shell Programming and Scripting
Hi friends, I want to convert 24 hour timing to 12 hour please help me...
my data file looks like this..
13-Nov-2011 13:27:36 15.32044 72.68502
13-Nov-2011 12:08:31 15.31291 72.69807
16-Nov-2011 01:16:54 15.30844 72.74028
15-Nov-2011 20:09:25 15.35096 ... (13 Replies)
Discussion started by: nex_asp
13 Replies
9. Shell Programming and Scripting
I have a cron: 0 5,11,17,23 * * * /home/oracle/scripts/sysize.ksh
This cron will trigger
cat dbsz.txt | mail -s "$TODAY: PROD DB Size" $RECIPIENTS
I don't want to get the e-mail notice 4 times a day. Can I have just one e-mail triggered at 11 AM?
Please advise.
Thank you (3 Replies)
Discussion started by: Daniel Gate
3 Replies
10. Shell Programming and Scripting
Hi All,
While setting the crontab i am getting the below error,
"/tmp/crontab.XXXXwKymEc" 156L, 15621C written
crontab: installing new crontab
"/tmp/crontab.XXXXwKymEc":74: bad hour
Please help.
Thanks (2 Replies)
Discussion started by: nag_sathi
2 Replies
LEARN ABOUT DEBIAN
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.10 1 Mar 1994 queuedefs(4)