Schedule Job Fortnightly (FRI) in Crontab


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Schedule Job Fortnightly (FRI) in Crontab
# 8  
Old 09-03-2013
Quote:
Originally Posted by Chubler_XL
Also at now is not a valid way to test crontab entries particularly these ones with escaped percent symbols.

You are better off just writing a script that updates/appends to a logfile and scheduling it for 5 or 10 mins in the future and waiting for cron to run it.
It's easier to make a crontab entry to run every Friday and have the 1st test in the script that is run kick off the real job if it is an even week (or run the real job if it is an odd week as shown in earlier posts).
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to schedule crontab?

Hi All, How to schedule crontab on all day except sunday and monday means from tuesday to saturday at 06:00AM. (3 Replies)
Discussion started by: Riverstone
3 Replies

2. Shell Programming and Scripting

Crontab schedule

Hi all, I would like to schedule a crontab script, which should run From 8pm Thursday to 2am Friday and it should run every 10 minutes. I have put a script like below, is it the correct one. 10 01,02,20,21,22,23,00 * * 4-5 /u01/app/test.ksh Any other options available to schedule the same... (6 Replies)
Discussion started by: sid2013
6 Replies

3. AIX

job run before schedule on crontab

Guys, yesterday i just make a script with email as a result and put them into crontab, it will execute on 23.33. Today, i recieved email from system twice as result the script. the first email send at 23.02 and the second send at 23.33 how is the script execute two times ? the first job run... (6 Replies)
Discussion started by: michlix
6 Replies

4. Shell Programming and Scripting

schedule job

Hi, I have a spcific box called abc in autosys and below that there are 2 jobs. my requirement is to run the abc box only on monday and rest of the day the rest of the jobs should be in success status.. ---------- Post updated at 03:11 PM ---------- Previous update was at 02:45 PM ----------... (4 Replies)
Discussion started by: j_panky
4 Replies

5. Shell Programming and Scripting

Schedule a script to run at 10am from mon to fri

Hi, I need to write a shell script which will run i background and will execute other script only on Mon to Fri 10 AM but not on Sat and Sun. I am able to set it to run on every day at 10AM but how to make it to run only on Mon to Fri Thanks, Firestar. (7 Replies)
Discussion started by: firestar
7 Replies

6. AIX

Schedule Job

how to schedule a job in aix, pls explain with cmd (1 Reply)
Discussion started by: udtyuvaraj
1 Replies

7. Shell Programming and Scripting

Schedule a job using Crontab

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

8. Solaris

crontab to run mon.wed.fri

I have it set to the following 0 9 * * 1,3,5 /var/tmp/sys_diag It ran correctly on Wednesday but did not run on Friday and I am not sure why, does the above appear to be correct? (3 Replies)
Discussion started by: deaconf19
3 Replies

9. UNIX for Dummies Questions & Answers

Crontab schedule

I have the following crontab entry. 0,30 00-16 * * * This job runs every 30 minutes between the hours of 12:00AM and 4:00PM. How can I have it stop at 4:30PM instead? Thank you, David (3 Replies)
Discussion started by: dkranes
3 Replies

10. UNIX for Advanced & Expert Users

How to schedule a job

Hi, How can i schedule a job, i.e a program named p found at path a/b/c, to run at a time T everyday? Thanks (5 Replies)
Discussion started by: ashvik
5 Replies
Login or Register to Ask a Question
At(3pm) 						User Contributed Perl Documentation						   At(3pm)

NAME
Schedule::At - OS independent interface to the Unix 'at' command SYNOPSIS
require Schedule::At; Schedule::At::add(TIME => $string, COMMAND => $string [, TAG =>$string]); Schedule::At::add(TIME => $string, COMMAND => @array [, TAG =>$string]); Schedule::At::add(TIME => $string, FILE => $string) %jobs = Schedule::At::getJobs(); %jobs = Schedule::At::getJobs(JOBID => $string); %jobs = Schedule::At::getJobs(TAG => $string); Schedule::At::readJobs(JOBID => $string); Schedule::At::readJobs(TAG => $string); Schedule::At::remove(JOBID => $string); Schedule::At::remove(TAG => $string); DESCRIPTION
This modules provides an OS independent interface to 'at', the Unix command that allows you to execute commands at a specified time. Schedule::At::add Adds a new job to the at queue. You have to specify a TIME and a command to execute. The TIME has a common format: YYYYMMDDHHmm where YYYY is the year (4 digits), MM the month (01-12), DD is the day (01-31), HH the hour (00-23) and mm the minutes. The command is passed with the COMMAND or the FILE parameter. COMMAND can be used to pass the command as an string, or an array of commands, and FILE to read the commands from a file. The optional parameter TAG serves as an application specific way to identify a job or a set of jobs. Returns 0 on success or a value != 0 if an error occurred. Schedule::At::readJobs Read the job content identified by the JOBID or TAG parameters. Returns a hash of JOBID => $string where $string is the the job content. As the operating systems usually add a few environment settings, the content is longer than the command provided when adding the job. Schedule::At::remove Remove an at job. You identify the job to be deleted using the JOBID parameter (an opaque string returned by the getJobs subroutine). You can also specify a job or a set of jobs to delete with the TAG parameter, removing all the jobs that have the same tag (as specified with the add subroutine). Used with JOBID, returns 0 on success or a value != 0 if an error occurred. Used with TAG, returns a hash reference where the keys are the JOBID of the jobs found and the values indicate the success of the remove operation. Schedule::At::getJobs Called with no params returns a hash with all the current jobs or dies if an error has occurred. It's possible to specify the TAG or JOBID parameters so only matching jobs are returned. For each job the key is a JOBID (an OS dependent string that shouldn't be interpreted), and the value is a hash reference. This hash reference points to a hash with the keys: TIME An OS dependent string specifying the time to execute the command TAG The tag specified in the Schedule::At::add subroutine Configuration Variables o $Schedule::At::SHELL This variable can be used to specify shell for execution of the scheduled command. Can be useful for example when scheduling from CGI script and the account of the user under which httpd runs is locked by using '/bin/false' or similar as a shell. EXAMPLES
use Schedule::At; # 1 Schedule::At::add (TIME => '199801181530', COMMAND => 'ls', TAG => 'ScheduleAt'); # 2 @cmdlist = ("ls", "echo hello world"); Schedule::At::add (TIME => '199801181630', COMMAND => @cmdlist, TAG => 'ScheduleAt'); # 3 Schedule::At::add (TIME => '199801181730', COMMAND => 'df'); # This will remove #1 and #2 but no #3 Schedule::At::remove (TAG => 'ScheduleAt'); my %atJobs = Schedule::At::getJobs(); foreach my $job (values %atJobs) { print " ", $job->{JOBID}, " ", $job->{TIME}, ' ', ($job->{TAG} || ''), " "; } AUTHOR
Jose A. Rodriguez (jose AT rodriguez.jp) perl v5.14.2 2012-04-24 At(3pm)