Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: AIX cron job is running everyday instead of on a particular day
Operating Systems AIX AIX cron job is running everyday instead of on a particular day Post 303023465 by rbatte1 on Monday 17th of September 2018 11:54:42 AM
Old 09-17-2018
Yes, I fell over the some 20 years ago with the same result. It seems that cron does not make sure that all conditions for the day match, so you may find that it runs every day between 15th & 21st each month AND every Sunday.

You would think that what you have set up is perfectly sensible, but sadly the cron designers had other ideas.

I got round this by running a shell script everyday that decided if I was on the correct day and correct week, and if so then it progressed to run the script I really wanted. it is annoying and I sympathise, but that was my way round it.



From the crontab file manual (man 5 crontab) I get this:-
Quote:
Note: The day of a command's execution can be specified by two fields - day of month, and day of week. If both fields are restricted (ie, aren't *), the command will be run when
either field matches the current time. For example,
"30 4 1,15 * 5" would cause a command to be run at 4:30 am on the 1st and 15th of each month, plus every Friday.

I hope that this helps,
Robin
This User Gave Thanks to rbatte1 For This Post:
Kumar7997
 

10 More Discussions You Might Find Interesting

1. HP-UX

Cron Job Not Running

Hi, I have a cron schedule like this 04,16,28,40,52 * * * * /nag/startProcessABatch (unix script) i want to add new lines in this file (like Logging), i just copy this file into a /tmp folder (for backup copy), and i have edited this file (added few lines of code for logging). ... (1 Reply)
Discussion started by: nag_sundaram
1 Replies

2. UNIX for Advanced & Expert Users

cron job is not running

hi, i have the following line in the crontab 15 5 * * 6 /home/adw/BCE_ADW.pl The problem is the cron job is not getting started automatically. But this was working til last week. now it is not working. what could be the problem. Any idea? (3 Replies)
Discussion started by: Suguna
3 Replies

3. UNIX for Dummies Questions & Answers

Cron job not running

Hi All, I am editing crontab using -e option to add a new job Below is the line 30 * * * * scriptpath This job is not executing every thirty minutes. I have checked, cron daemon is running. What did I miss? Can some one help? I am using cron shell..ksh (7 Replies)
Discussion started by: yabhi_22
7 Replies

4. Shell Programming and Scripting

Cron job randomly once a day

I want to create a cron job randomly once a day for my site's registration. The responsible file for registrations is a config file and I need to change the contents twice on day (on and off) I know the way for random cron job for example */n * * * * /usr/local/bin/php... (6 Replies)
Discussion started by: lucker
6 Replies

5. UNIX for Advanced & Expert Users

Autosys Job Running every 5th Day of Month

Hi, Is there a way to schedule a job in Autosys to run every 5th Day of Month without using custom calendar? Thanks. (1 Reply)
Discussion started by: vbhatnag
1 Replies

6. Solaris

Cron job is not running

Hi, I have set up the crontab as follows. root@IDC4VASAPP07 # crontab -l 0-59 * * * * /var/tmp/r.sh 0-59 * * * * date >> /var/tmp/log root@IDC4VASAPP07 # r.sh is as follows. root@IDC4VASAPP07 # cat r.sh #!/bin/bash dt1=$(perl -e 'use POSIX;print strftime... (10 Replies)
Discussion started by: SunilB2011
10 Replies

7. Shell Programming and Scripting

Adding a cron job that will execute everyday at 14:50 hrs

Hi I want to execute a cron job everyday at 14:50 hrs. I have a script like this: TMP_FILE="/tmp/tmpcron.txt" RES=0 /usr/bin/crontab -l >> $TMP_FILE ADD_JOB="50 14 * * * /opt/mypath/scriptname.sh" grep "scriptname.sh" $TMP_FILE >> /dev/null JOB_NOT_EXIST=$? if test $JOB_NOT_EXIST... (2 Replies)
Discussion started by: saurabhkoar
2 Replies

8. UNIX for Advanced & Expert Users

Run A Job in Cron On A Specific Day Excluding Holidays

Hi, I want to run a job in cron on a specific date(say 25th of every month) excluding holidays. Can anyone provide some hints to do this? Thanks for any inputs. (1 Reply)
Discussion started by: sktkpl
1 Replies

9. Solaris

Cron job running even after cron is removed

Hi , I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility ) I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies

10. Shell Programming and Scripting

CRON job still running?

Hi All, I am writing a script that will eventually be executed by a cron job every 15 minutes. I want to make sure that my logic/script doesn't get executed if a previous job is still running. What would be the best way to handle that scenario? I was thinking to make my script create a temporary... (1 Reply)
Discussion started by: rdogadin
1 Replies

LEARN ABOUT HPUX

queuedefs

queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and crontab

SYNOPSIS

DESCRIPTION

       The  file  describes  the characteristics of the queues managed by (see cron(1M)).  Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

	      [njob[nice[nwait

       The fields in this line are:

	      q 	The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for  jobs  started	by
			(see  at(1)),  and  is	the  queue  for jobs run from a file (see crontab(1)).	Queue names through designate user-defined
			queues.

	      njob	The maximum number of jobs that can be run simultaneously in that queue.  Although any number can be specified here,  (see
			cron(1M))  by  default limits the number of jobs that can be run on all the queues to 100.  This limitation can be removed
			by setting the variable to 1 in the file.

	      nice	The value to give to all jobs in that queue that are not run with a user ID of	super-user  (see  nice(1)).   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 more than 100 jobs were running in all the queues (see njob above).

EXAMPLES

       Consider the following file:

       The file is interpreted as follows:

	      The	     queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
			     1.

			     Since  no	nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
			     before trying again to run it (see cron(1M)).

	      The	     queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously.  Those jobs will be run with a value of 2.
			     If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because
       too many other jobs are running, will wait 60 seconds before trying again to run it.

SEE ALSO

       at(1), nice(1), crontab(1), cron(1M), proto(4).

STANDARDS CONFORMANCE

																      queuedefs(4)
All times are GMT -4. The time now is 06:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy