Sponsored Content
Top Forums Shell Programming and Scripting Unix scheduler other than Cron Post 302171025 by DukeNuke2 on Wednesday 27th of February 2008 10:53:02 AM
Old 02-27-2008
there is a tool called "anacron"... maybe this works?

anacron - Wikipedia, the free encyclopedia
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

command to schedule a unix script in tidal' scheduler

hi i am needed to use tidal's scheduler to schedule unix scripts available on server A. while creating a job to be scheduled, it has an option called command which will take a path of the file. i have seen several examples in the following way e:\tidal\bin\sleep.exe here i did not understand two... (0 Replies)
Discussion started by: balireddy_77
0 Replies

2. Shell Programming and Scripting

Job scheduler without using cron

Hi, I want to schedule the scripts/batches to run simultaneously. I had all the information in the config (flat)file, which contains script name, time, dependency, path, priority and status etc., I want to run the jobs parellelly and some jobs are required to give the input. How can I do this?... (1 Reply)
Discussion started by: sharif
1 Replies

3. Solaris

CRON Scheduler

I have akorn shell job that I can run manually but when I run via cron it starts and finishes, but does not do what it does when I run it manually. Any ideals on why this is happening? (3 Replies)
Discussion started by: CAGIRL
3 Replies

4. HP-UX

Unix - Cron Job Help

Up until now I used Oracle's Enterprise manager to submit the batch job. However its SMTP function (Sends EMail about Job status) is unstable lately. I want to use Unix's Cron to submit my batch job. This way I can also eliminate the middle layer (Oracle's Enterprise manager). Please help how I can... (1 Reply)
Discussion started by: aixhp
1 Replies

5. UNIX for Dummies Questions & Answers

CRON JOB SCHEDULER throwing "option not allowed error"

Hi All, Pardon me if this turns out to be a dumb question. But I am trying to schedule a cron job for a my script which takes input options. So an entry in crontab would be something like: 1 * * * * run_report.sh -o out.csv -m monthly -e somename@email.com > cron_output.log 2> cron_error.log... (3 Replies)
Discussion started by: trueharsh
3 Replies

6. Shell Programming and Scripting

Help needed regarding cron job scheduler with CyberArk Password security

Hi All, I have a script which will restart some web server and bring it up again. For that I need to retrieve 3 password from CyberArk (Cyber-Ark - Wikipedia, the free encyclopedia) vault. My question is: Is this possible to schedule the script through cron and automatic password... (0 Replies)
Discussion started by: saps19
0 Replies

7. UNIX for Advanced & Expert Users

CRON on Unix Server

What is the command to list out all the CRON's running on a UNIX Server (7 Replies)
Discussion started by: Pash
7 Replies

8. Red Hat

Cron scheduler issue

I am trying to schedule a script in Linux to between 8th and the 31st of each month on Sundays @ 6:50 only and i scheduled it as follows: 50 6 8-31 * 0 ksh /home/cpac/SPID_Files/GetFiles.ksh Which did it run on the 8th on Saturday instead of only Sundays !!! (3 Replies)
Discussion started by: mrn6430
3 Replies

9. UNIX for Advanced & Expert Users

OS Watcher not running with cron scheduler

Hi team, O.S : Oracle Linux Issue : I am facing issue when running OS watcher script from cron scheduler. But when i run the same command manually, its getting executed. Note : I have to press " Enter " button to get out of the blank screen when I execute the script manually. Below is... (1 Reply)
Discussion started by: madhuraju
1 Replies

10. UNIX for Beginners Questions & Answers

Program not running from the cron scheduler

Good Afternoon, I have a sh script that the admin added to the cron schedule. It runs fine when I run it manually...but not when scheduled. I added the path that is found for my user to the script. Still no luck. Any ideas what I should look at? Thanks Marty (8 Replies)
Discussion started by: MSpeare
8 Replies
ANACRON(8)						       System Administration							ANACRON(8)

NAME
anacron - runs commands periodically SYNOPSIS
anacron [-s] [-f] [-n] [-d] [-q] [-t anacrontab] [-S spooldir] [job] anacron [-S spooldir] -u [-t anacrontab] [job] anacron [-V|-h] anacron -T [-t anacrontab] DESCRIPTION
Anacron is used to execute commands periodically, with a frequency specified in days. Unlike cron(8), it does not assume that the machine is running continuously. Hence, it can be used on machines that are not running 24 hours a day to control regular jobs as daily, weekly, and monthly jobs. Anacron reads a list of jobs from the /etc/anacrontab configuration file (see anacrontab(5)). This file contains the list of jobs that Anacron controls. Each job entry specifies a period in days, a delay in minutes, a unique job identifier, and a shell command. For each job, Anacron checks whether this job has been executed in the last n days, where n is the time period specified for that job. If a job has not been executed in n days or more, Anacron runs the job's shell command, after waiting for the number of minutes specified as the delay parameter. After the command exits, Anacron records the date (excludes the hour) in a special timestamp file for that job, so it knows when to execute that job again. When there are no more jobs to be run, Anacron exits. Anacron only considers jobs whose identifier, as specified in anacrontab(5), matches any of the job command-line arguments. The job com- mand-line arguments can be represented by shell wildcard patterns (be sure to protect them from your shell with adequate quoting). Speci- fying no job command-line arguments is equivalent to specifying "*" (that is, all jobs are considered by Anacron). Unless Anacron is run with the -d option (specified below), it forks to the background when it starts, and any parent processes exit imme- diately. Unless Anacron is run with the -s or -n options, it starts jobs immediately when their delay is over. The execution of different jobs is completely independent. If an executed job generates any output to standard output or to standard error, the output is mailed to the user under whom Anacron is running (usually root), or to the address specified in the MAILTO environment variable in the /etc/anacrontab file, if such exists. If the LOGNAME environment variable is set, it is used in the From: field of the mail. Any informative messages generated by Anacron are sent to syslogd(8) or rsyslogd(8) under with facility set to cron and priority set to notice. Any error messages are sent with the priority error. "Active" jobs (i.e., jobs that Anacron already decided to run and are now waiting for their delay to pass, and jobs that are currently being executed by Anacron), are "locked", so that other copies of Anacron cannot run them at the same time. OPTIONS
-f Forces execution of all jobs, ignoring any timestamps. -u Updates the timestamps of all jobs to the current date, but does not run any. -s Serializes execution of jobs. Anacron does not start a new job before the previous one finished. -n Runs jobs immediately and ignores the specified delays in the /etc/anacrontab file. This options implies -s. -d Does not fork Anacron to the background. In this mode, Anacron will output informational messages to standard error, as well as to syslog. The output of any job is mailed by Anacron. -q Suppresses any messages to standard error. Only applicable with -d. -t some_anacrontab Uses the specified anacrontab, rather than the /etc/anacrontab default one. -T Anacrontab testing. Tests the /etc/anacrontab configuration file for validity. If there is an error in the file, it is shown on the standard output and Anacron returns the value of 1. Valid anacrontabs return the value of 0. -S spooldir Uses the specified spooldir to store timestamps in. This option is required for users who wish to run anacron themselves. -V Prints version information, and exits. -h Prints short usage message, and exits. SIGNALS
After receiving a SIGUSR1 signal, Anacron waits for any running jobs to finish and then exits. This can be used to stop Anacron cleanly. NOTES
Make sure your time-zone is set correctly before Anacron is started since the time-zone affects the date. This is usually accomplished by setting the TZ environment variable, or by installing a /usr/lib/zoneinfo/localtime file. See tzset(3) for more information. Timestamp files are created in the spool directory for each job specified in an anacrontab. These files are never removed automatically by Anacron, and should be removed by hand if a job is no longer being scheduled. FILES
/etc/anacrontab Contains specifications of jobs. See anacrontab(5) for a complete description. /var/spool/anacron This directory is used by Anacron for storing timestamp files. SEE ALSO
anacrontab(5), cron(8), tzset(3) The Anacron README file. BUGS
Anacron never removes timestamp files. Remove unused files manually. Anacron uses up to two file descriptors for each active job. It may run out of descriptors if there are lots of active jobs. See echo $(($(ulimit -n) / 2)) for information how many concurent jobs anacron may run. Mail comments, suggestions and bug reports to Sean 'Shaleh' Perry <shaleh@(debian.org|valinux.com)>. AUTHOR
Anacron was originally conceived and implemented by Christian Schwarz <schwarz@monet.m.isar.de>. The current implementation is a complete rewrite by Itai Tzur <itzur@actcom.co.il>. The code base was maintained by Sean 'Shaleh' Perry <shaleh@(debian.org|valinux.com)>. Since 2004, it is maintained by Pascal Hakim <pasc@(debian.org|redellipse.net)>. For Fedora, Anacron is maintained by Marcela MaAilAiAovA <mmaslano@redhat.com>. cronie 2012-11-22 ANACRON(8)
All times are GMT -4. The time now is 07:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy