Sponsored Content
Full Discussion: Setting cronjobs...
Top Forums Shell Programming and Scripting Setting cronjobs... Post 302202869 by incredible on Friday 6th of June 2008 12:48:30 AM
Old 06-06-2008
You can run multiple cronjobs at a time without clashing in Unix. Each will run as a background process.
Add this tag at the end of your cron job:

>/dev/null 2>&1

Example of your cron job looks like:

30 23 * * * /home/username/www/cgi-bin/members.cgi> /dev/null 2>&1
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

cronjobs

hi How can I add a cronjob to the crontab file? to execute a shel script named testScript.sh every day at 00:00. Thanks (3 Replies)
Discussion started by: tamer
3 Replies

2. AIX

Cronjobs

We recently upgrade from AIX 4.3.3 to AIX 5.3, We noticed that some cronjobs that run for our programmers did not fire off this morning. You can crontab -l and -e and see the jobs. Did AIX 5.3 change something? Thanks Mike (1 Reply)
Discussion started by: mcastill66
1 Replies

3. UNIX for Advanced & Expert Users

Delete Duplicate Cronjobs

I set up same cronjobs in two different users to generate messages at 5:30 AM Not Its generating duplicate messages. I want to delete the cron entries set up in the first user, but I am unable to view the entries in that user. I tried to find the process Id, but its not showing any id Could... (2 Replies)
Discussion started by: nskworld
2 Replies

4. Linux

Cronjobs stopped working

Hi All, I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that. Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies

5. Solaris

cronjobs not running.

hi friends, how to check if the cronjobs is not running and how to make it run again. (1 Reply)
Discussion started by: cromohawk
1 Replies

6. Shell Programming and Scripting

cronjobs stopped working

Hello people, I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now. Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies

7. Shell Programming and Scripting

Setting up cronjobs

hello all, I have a shell script and I need to schedule it in crontab, I have the next line: 06 16 * * 1,2,3,4,5 /usr/bin/ksh /path/path/name.sh > /path/path/name.log first, I scheduled from Monday to Friday but it doesn't run, the log file is empty.. any idea why is causing this?... (14 Replies)
Discussion started by: Geller
14 Replies

8. UNIX for Dummies Questions & Answers

Is this possible with cronjobs?

Hi there, i've a question about cronjobs. I'm creating a concept for a centralized logging repository using log4j/log4net. Sadly the appenders I want to use (fileappenders) aren't telegram based but need a permanent stream to the repository. Because I can not assure this I want to log these... (6 Replies)
Discussion started by: collatz
6 Replies

9. Shell Programming and Scripting

Facing issues with cronjobs

Hello Everyone, We have a cronjob scheduled to pick up files from one system and transfer to another system. the underlying code is a shell script. These cronjobs were working correctly until sometime. 2 days back they did not pick up the scripts but created empty logs. However when we tried... (6 Replies)
Discussion started by: Rads
6 Replies

10. Solaris

How to find all Cronjobs?

Hey Guys, i've got a big issue... I've to find all running scripts in all crontabs. Is there a possibility to display all crontabs of each user? What i've already tried? The following script: for user in $(cut -f1 -d: /etc/passwd); do crontab -l $user; done I'm already root but i didn't... (3 Replies)
Discussion started by: Marcusg562
3 Replies
ANACRON(8)						       Anacron Users' Manual							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 can be 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 aren't running 24 hours a day, to control daily, weekly, and monthly jobs that are usually controlled by cron. When executed, Anacron reads a list of jobs from a configuration file, normally /etc/anacrontab (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 period specified for that job. If not, 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 in a special timestamp file for that job, so it can know when to execute it again. Only the date is used for the time calculations. The hour is not used. When there are no more jobs to be run, Anacron exits. Anacron only considers jobs whose identifier, as specified in the anacrontab matches any of the job command-line arguments. The job argu- ments can be shell wildcard patterns (be sure to protect them from your shell with adequate quoting). Specifying no job arguments, is equivalent to specifying "*" (That is, all jobs will be considered). Unless the -d option is given (see below), Anacron forks to the background when it starts, and the parent process exits immediately. Unless the -s or -n options are given, Anacron starts jobs immediately when their delay is over. The execution of different jobs is com- pletely independent. If a job generates any output on its standard output or standard error, the output is mailed to the user running Anacron (usually root), or to the address contained by the MAILTO environment variable in the crontab, if such exists. If the LOGNAME environment variable is set, it will be used as From: field. Informative messages about what Anacron is doing are sent to syslogd(8) under facility cron, priority notice. Error messages are sent at priority error. "Active" jobs (i.e. jobs that Anacron already decided to run and now wait for their delay to pass, and jobs that are currently being exe- cuted by Anacron), are "locked", so that other copies of Anacron won't run them at the same time. OPTIONS
-f Force execution of the jobs, ignoring the timestamps. -u Only update the timestamps of the jobs, to the current date, but don't run anything. -s Serialize execution of jobs. Anacron will not start a new job before the previous one finished. -n Run jobs now. Ignore the delay specifications in the /etc/anacrontab file. This options implies -s. -d Don't fork to the background. In this mode, Anacron will output informational messages to standard error, as well as to syslog. The output of jobs is mailed as usual. -q Suppress messages to standard error. Only applicable with -d. -t anacrontab Use specified anacrontab, rather than the default -T Anacrontab testing. The configuration file will be tested for validity. If there is an error in the file, an error will be shown and anacron will return 1. Valid anacrontabs will return 0. -S spooldir Use the specified spooldir to store timestamps in. This option is required for users who wish to run anacron themselves. -V Print version information, and exit. -h Print short usage message, and exit. SIGNALS
After receiving a SIGUSR1 signal, Anacron waits for running jobs, if any, to finish and then exits. This can be used to stop Anacron cleanly. NOTES
Make sure that the time-zone is set correctly before Anacron is started. (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 in anacrontab. These 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 more than about 125 active jobs (on normal kernels). 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)>. Pascal Hakim 2004-07-11 ANACRON(8)
All times are GMT -4. The time now is 02:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy