10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am working with oracle, and want to make a scheduler program by using cron job..
I've done with shell script that calls oracle stored procedure. It works.
However, when I call the script through crontab, it is failed. :(
Here is the error message:
Cron: The previous message... (2 Replies)
Discussion started by: rmard
2 Replies
2. UNIX for Dummies Questions & Answers
Hi, can someone explain the differences between using the at and crontab commands. When would you use one command over the other?
TIA
Dom (1 Reply)
Discussion started by: domburf69
1 Replies
3. Shell Programming and Scripting
I have a crontab entry,but it is not working.
Can anybody help me in this regard?? (2 Replies)
Discussion started by: Sourav_Paul
2 Replies
4. UNIX for Advanced & Expert Users
Dear All
jobs are scheduled in crontab . To view this I use crontab -l . But suddenly today I am not able to see any jobs that is being scheduled in crontab. when I type crontab -l , I am seeing nothing.I am not logging through admin user(i dont have it).But I can schedule jobs through... (3 Replies)
Discussion started by: tkbharani
3 Replies
5. Shell Programming and Scripting
Hi All,
I've a shell script which calls a Sybase stored procedure to do some functionality. I want to schedule the running of this script by crontab. I'm using Solaris 5.8. When i executed the following command
crontab -l
i got the output as
crontab: can't open your crontab file
How... (10 Replies)
Discussion started by: sumesh.abraham
10 Replies
6. UNIX for Dummies Questions & Answers
hi all
how to schedule the crontab file in unix? (2 Replies)
Discussion started by: ss4u
2 Replies
7. Shell Programming and Scripting
i have a ksh script that creates messages in a temp directory and then sends them out using the sendmail command and i'm trying to set it up to run every night with crontab.
So the basic gist of the script is
#create temp dir and messages
...
#loop through each message and send using sendmail... (3 Replies)
Discussion started by: bob122480
3 Replies
8. UNIX for Dummies Questions & Answers
How can I run "crontab" (parameters) every 6 hours on solaris machine?
Thanks (1 Reply)
Discussion started by: gen4ik
1 Replies
9. UNIX for Dummies Questions & Answers
dear all ,
does any one now how can i become sure that the crontab that i put was working successfully not by looking for thr result of the sheduled task but from a log for the crontab or something similar
and i need to check that the cron i wrote is correct
00 15 * * 0,1,2,3,6... (2 Replies)
Discussion started by: habuzahra
2 Replies
10. UNIX for Dummies Questions & Answers
Hi
I have a shell script which works fine at the command line
and does works in crontab also but does not send the output to
mail as other scripts do by default.
10 1 * * * /export/home/test/report_script
by default should send the output to mail but the script
runs OK and the output... (1 Reply)
Discussion started by: run_time_error
1 Replies
CRONTAB(1) User Commands CRONTAB(1)
NAME
crontab - maintains crontab files for individual users
SYNOPSIS
crontab [-u user] file
crontab [-u user] [-l | -r | -e] [-i] [-s]
crontab -n [ hostname ]
crontab -c
DESCRIPTION
Crontab is the program used to install, remove or list the tables used to serve the cron(8) daemon. Each user can have their own crontab,
and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in MLS mode, you can define more
crontabs for each range. For more information, see selinux(8).
In this version of Cron it is possible to use a network-mounted shared /var/spool/cron across a cluster of hosts and specify that only one
of the hosts should run the crontab jobs in the particular directory at any one time. You may also use crontab(1) from any of these hosts
to edit the same shared set of crontab files, and to set and query which host should run the crontab jobs.
Running cron jobs can be allowed or disallowed for different users. For this purpose, use the cron.allow and cron.deny files. If the
cron.allow file exists, a user must be listed in it to be allowed to use cron If the cron.allow file does not exist but the cron.deny file
does exist, then a user must not be listed in the cron.deny file in order to use cron. If neither of these files exists, only the super
user is allowed to use cron. Another way to restrict access to cron is to use PAM authentication in /etc/security/access.conf to set up
users, which are allowed or disallowed to use crontab or modify system cron jobs in the /etc/cron.d/ directory.
The temporary directory can be set in an environment variable. If it is not set by the user, the /tmp directory is used.
OPTIONS
-u Appends the name of the user whose crontab is to be modified. If this option is not used, crontab examines "your" crontab, i.e.,
the crontab of the person executing the command. Note that su(8) may confuse crontab, thus, when executing commands under su(8) you
should always use the -u option. If no crontab exists for a particular user, it is created for him the first time the crontab -u
command is used under his username.
-l Displays the current crontab on standard output.
-r Removes the current crontab.
-e Edits the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor,
the modified crontab will be installed automatically.
-i This option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
-s Appends the current SELinux security context string as an MLS_LEVEL setting to the crontab file before editing / replacement occurs
- see the documentation of MLS_LEVEL in crontab(5).
-n This option is relevant only if cron(8) was started with the -c option, to enable clustering support. It is used to set the host in
the cluster which should run the jobs specified in the crontab files in the /var/spool/cron directory. If a hostname is supplied,
the host whose hostname returned by gethostname(2) matches the supplied hostname, will be selected to run the selected cron jobs
subsequently. If there is no host in the cluster matching the supplied hostname, or you explicitly specify an empty hostname, then
the selected jobs will not be run at all. If the hostname is omitted, the name of the local host returned by gethostname(2) is
used. Using this option has no effect on the /etc/crontab file and the files in the /etc/cron.d directory, which are always run,
and considered host-specific. For more information on clustering support, see cron(8).
-c This option is only relevant if cron(8) was started with the -c option, to enable clustering support. It is used to query which
host in the cluster is currently set to run the jobs specified in the crontab files in the directory /var/spool/cron , as set using
the -n option.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
An informative usage message appears if you run a crontab with a faulty command defined in it.
AUTHOR
Paul Vixie <vixie@isc.org>
Colin Dean <colin@colin-dean.org>
cronie 2012-11-22 CRONTAB(1)