09-17-2013
There may be more to it the simply checking one crontab. You did not specify what user(s): usually there are root, sys, and other system or application specific crontab files.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Am trying to write a script that will monitor `cron`, obviously this can only be done from another box (so I've figured) but I'm having a spot of bother...
We have two SCO 5.0.5 Unix boxes (.82 & .84).
I have the following script running on the .82 box presently.. being run from cron every 15... (1 Reply)
Discussion started by: Cameron
1 Replies
2. Shell Programming and Scripting
Hi All
I am trying to run a .sh file from cron but its not performing its intended purpose, though the same sh file works fine when triggered manually.Following mail I recieve when it tries to run the script.
*********************************************************
To: wlsdev05
Subject:... (16 Replies)
Discussion started by: pankajkrmishra
16 Replies
3. UNIX for Advanced & Expert Users
Hi,
Anyone please let me know how to add an entry for crontab while there are few of entries already in.
When I execute crontab -e, the entries which are added already are displayed. But, I need to add one more entry to the crontab and then after that I need to remove the entry without... (1 Reply)
Discussion started by: minar
1 Replies
4. UNIX for Dummies Questions & Answers
can anybody explain the usage of CRON for adding a cron job. please provide an example also for better understanding !!!
Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies
5. Solaris
hi,
how i woulsd be able to find that my cron job is running or not..
E.g abc (2 Replies)
Discussion started by: sam.whocares
2 Replies
6. Solaris
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies
7. Shell Programming and Scripting
I have to monitor several processes in my application .
i get the listing of these processes using the command ps -ax
i want to write a shell script that will monitor the processes and if a
process goes missing then it will send an email to my gmail account.
I want to run this... (6 Replies)
Discussion started by: asalman.qazi
6 Replies
8. Shell Programming and Scripting
Hi
I have a script in cron entry
55 15-22 * * * /clocal/rcc/user/dgircc/bin/appcontext/dcClearAppContext.ksh TEST >/tmp/dcClearAppContext.out 2>&1
how can i monitor the script whether it has run each time thriygh or not ?
how can i monitor multiple scripts of this kind through a script... (5 Replies)
Discussion started by: mskalyani
5 Replies
9. Solaris
Hi ,
I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility )
I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies
10. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration
parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD