Vino has already mentioned one possibility. Another one would be: find out the PIDs of the background processes and set up a while-loop which scans the process table for these PIDs. Find an example below for one such process:
Hello:
If I want to run a crontab every hour between 9 am to 9pm, will this work
00 09-19 * * * /.../.../../program.sh
If the above does not work, what should it be ??
Thanks, ST2000 (4 Replies)
need help to write crontab
my crontabe file every minute to rsh and check that it is running or not
i want to change it on every 1o minute please help me
example of my crontab
#check if system is running
* * * * * rsh metal3 /users/test/run.server
i want to check that every 10... (2 Replies)
Hi All
I have a requirement to schedule my script through cron tab.
I have 2 scripts to schedule.
Case1:My script should run every day in the server.It should be triggered in every 2 mins interval.i.e suppose i implemented the script now my script should run every 2 mins.How can i... (6 Replies)
Hi All,
I am required to make a crontab entry, I have the below requirement:
1. It should execute at 06:15 12:00 and 18:30
2. It should execute every day of the month for all the 30 days
I am going to add the below entry in the crontab file.
15,0,30 6,12,18 * * 0-6 cd... (3 Replies)
Hi
In my Unix server more than 500 cron jobs are scheduled daily and weekly basics.
Now,I would like to know only list of JOBs,which are running only on 14th of every month?
How can i find only which are all jobs will be scheduled only on 14th.
Please tell me the script. (4 Replies)
Hi,
We have a couple of jobs are scheduled in CRONTAB.
Now. I want generate a report for each job how many times ran successful and failed in a 1 month of time period.
is there any way to find in CRONTAB.
Please advise on this. (1 Reply)
Hi,
I have a cron tab file , which executes a particular script in a scheduled time and creates a output file. Since the cron tab file was created by the root , there is no access permission( for the output files) for other users irrespective of the default directory permission on which the... (5 Replies)
Hi,
I need to install the crontab utility in Ubuntu.
Can any one one tell me what exactly is the steps to do it?
Thanks in Advanced (2 Replies)
Discussion started by: diehard
2 Replies
LEARN ABOUT SUSE
cron
CRON(8) System Manager's Manual CRON(8)NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO crontab(1), crontab(5), pam(8)AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)