Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Understanding cron scheduling command Post 302286632 by vgersh99 on Wednesday 11th of February 2009 03:11:15 PM
Old 02-11-2009
Quote:
Originally Posted by niks
I think i got it..
20 * * * * - means that the job would be executed at 20th minute every hour.
*/20 * * * * - means that the job would be executed every 20 minutes..

is my understanding correct?
correcto mundo!
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

cron job scheduling

Hi, How can I configure cron file , to execute a script on evey alternate saturdays ? I am using AIX 5.0 machine Thanks in advance Shihab (1 Reply)
Discussion started by: shihabvk
1 Replies

2. UNIX for Dummies Questions & Answers

scheduling tasks with cron

hello there, i'm learning about task scheduling with cron and all seems hyper exciting, yeppie. But there is a prob: assume i have a script that needed to be executed at 7am everyday. I could do: vi mycron 00 7 * * * echo hi mother, i wanna be a script daddy. :wq crontab mycron how... (4 Replies)
Discussion started by: alikun
4 Replies

3. HP-UX

cron scheduling?

Hi all, i want a job to run first monday of every of month. (1 Reply)
Discussion started by: megh
1 Replies

4. UNIX for Advanced & Expert Users

Scheduling bi-weekly through cron

Is there a way in AIX to schedule a script to run bi-weekly through cron? I have a script that needs to run every other Wednesday, and this is what I thought I had to enter in the crontab file: 00 08 * * 3/2 /home/user/user.script It didn't like that. It reports a syntax error. I'm almost... (5 Replies)
Discussion started by: LPT
5 Replies

5. Shell Programming and Scripting

Scheduling Cron job-Problem

Hello All, I want to run a script for every 5 minutes interval.So i developed a script which has to be scheduled to run for every 5 minutes. That script internally runs another script. But the problem is it is not executing properly. Can anybody throw some light on this. Below are the code... (4 Replies)
Discussion started by: RSC1985
4 Replies

6. Shell Programming and Scripting

Scheduling a command to run every 3 days through cron

Hello, I have to schedule a command to run on every 3 days. Whether the below cron entry will work? 0 3 */3 * * command Please help me out and thanks in advance! (6 Replies)
Discussion started by: Arunprasad
6 Replies

7. UNIX for Dummies Questions & Answers

Scheduling tasks with cron in Slackware 12

How do I start, restart and stop the cron service under Slackware 12? (1 Reply)
Discussion started by: proactiveaditya
1 Replies

8. Shell Programming and Scripting

Cron Job Scheduling

Hi All, I have a script which is scheduled in the Cron. It runs every 10th and 40th min of an hour.The job has to run every 30min. But, I do not want to have the 00:10 MST run every day.Is it possible to exclude that run from the schedule?Or any other way through which i can run my job every... (4 Replies)
Discussion started by: sparks
4 Replies

9. UNIX for Dummies Questions & Answers

Cron confusion - scheduling a script

I have a script that backs up a directory, creates a log file and mails the log file to us. find . -print | backup -ivqf/dev/rmt0 | tee backup.log cat backup.log|mail -v -s "Tape backup log" maillist This script works fine from the console. When I schedule it in cron, I never get the... (1 Reply)
Discussion started by: landog
1 Replies

10. Red Hat

Scheduling cron job

Hi Everybody, I want to run a script at every 5 seconds. I know how to run it every 5 minutes, is there any possibility to run a script at 5 seconds interval. Regards, Mastan (3 Replies)
Discussion started by: mastansaheb
3 Replies
cron(1M)																  cron(1M)

NAME
cron - timed-job execution daemon SYNOPSIS
DESCRIPTION
executes commands at specified dates and times. Regularly scheduled commands can be specified according to instructions placed in files. Users can submit their own files with a command (see crontab(1)). Users can submit commands that are to be executed only once with an or command. Since never exits, it should be executed only once. This is best done by running from the initialization process with the startup script (see init(1M)). only establishes a schedule for files and or command files during process initialization and when it is notified by or that a file has been added, deleted, or modified. When executes a job, the job's user and group IDs are set to those of the user who submitted the job. Spring and Autumn Time Transitions On the days of daylight savings (summer) time transition (in time zones and countries where daylight savings time applies), schedules com- mands differently from normal. In the following description, an ambiguous time refers to an hour and minute that occurs twice in the same day because of a daylight sav- ings time transition (usually on a day during the Autumn season). A nonexistent time refers to an hour and minute that does not occur because of a daylight savings time transition (usually on a day during the Spring season). DST-shift refers to the offset that is applied to standard time to result in daylight savings time. This is normally one hour, but can be any combination of hours and minutes up to 23 hours and 59 minutes (see tztab(4)). When a command is specified to run at an ambiguous time, the command is executed only once at the occurrence of the ambiguous time. When a command is specified to run at a nonexistent time, the command is executed after the specified time by an amount of time equal to the DST-shift. When such an adjustment would conflict with another time specified to run the command, the command is run only once rather than running the command twice at the same time. Commands that are scheduled to run during all hours (there is a is in the hour field of the entry) are scheduled without any adjustment. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is set to the empty string, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). DIAGNOSTICS
A history of all actions taken by is recorded in EXAMPLES
The following examples assume that the time zone is In this time zone, the DST transition occurs one second before 2:00 a.m. and the DST- shift is 1 hour. Consider the following entries in a file: For the period of 1:00 a.m. to 4:00 a.m. on the days of DST transition, the results will be: Job Times Run in Fall Times Run in Spring ----------------------------------------------------- Job_1 01:00 MDT 01:00 MST Job_2 02:00 MDT 03:00 MDT Job_3 03:00 MST 03:00 MDT Job_4 04:00 MST 04:00 MDT Job_hourly 01:00 MDT 01:00 MST 02:00 MDT 02:00 MST 03:00 MST 03:00 MDT 04:00 MST 04:00 MDT Multiple_1 02:00 MDT 03:00 MST 03:00 MDT 04:00 MST 04:00 MDT Multiple_2 02:00 MDT 03:00 MDT 04:00 MST 04:00 MDT WARNINGS
In the Spring, when there is a nonexistent hour because of daylight savings time, a command that is scheduled to run multiple times during the nonexistent hour will only be run once. For example, a command scheduled to run at 2:00 and 2:30 a.m. in the time zone will only run at 3:00 a.m. The command that was scheduled at 2:30 a.m. will not be run at all, instead of running at 3:30 a.m. DEPENDENCIES
HP Process Resource Manager If the optional HP Process Resource Management (PRM) software is installed and configured, jobs are launched in the initial process resource group of the user that scheduled the job. The user's initial group is determined at the time the job is started, not when the job is scheduled. If the user's initial group is not defined, the job runs in the user default group See prmconfig(1) for a description of how to configure HP PRM, and prmconf(4) for a description of how the user's initial process resource group is determined. AUTHOR
was developed by AT&T and HP. FILES
Main directory Directory containing and job files Directory containing files Accounting information SEE ALSO
at(1), crontab(1), sh(1), init(1M), queuedefs(4), tztab(4). HP Process Resource Manager: prmconfig(1), prmconf(4) in STANDARDS CONFORMANCE
cron(1M)
All times are GMT -4. The time now is 10:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy