10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello
I have a problem with the crontab command
when I run a code containing Curl on the command line it runs without fail but as soon as I program it with crontab it executes everything except the curl returns fail
thank you for helping me to resolve this problem because since Monday I look... (14 Replies)
Discussion started by: beautymind
14 Replies
2. Shell Programming and Scripting
Hello all,
I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly.
My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but... (12 Replies)
Discussion started by: rusman
12 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I have two crontabs, one for the root and one for another user. There is a script in my configurations that has to send a email. The script works and sends the emails when I run it by hand with either the root or the user, and when I program it in the root's crontab.
But! It does not... (3 Replies)
Discussion started by: Tralaraloro
3 Replies
4. Shell Programming and Scripting
hi i have a script called test.sh. the content is ls >> crontest.txt.
if i run manually it's giving output.but if i scheduled in crontab it's not giving output.
crontab entry:
02 * * * * /sms5/SMSHOME/eds_sh/test.sh >> /sms5/SMSHOME/eds_sh/testfile/logfile 2>&1
I am using ksh.is there... (2 Replies)
Discussion started by: muraliinfy04
2 Replies
5. Shell Programming and Scripting
OS is Ubuntu 8.04.3. When I run the command:
/usr/bin/syslogMailer < /etc/syslog.pipes/criticalMessagesFrom a bash shell it works and i receive an email as per the script however when run from crontab it does not work. Can anyone explain why and how to fix it?
/usr/bin/syslogMailer... (4 Replies)
Discussion started by: jelloir
4 Replies
6. Shell Programming and Scripting
Hello Everyone,
I am logged in as me. I created a script in the directory "/install/new" called "script1.sh" which basically runs another script "runapp.sh" . The "runapp.sh" is a vendor provided application strart up script that came with the installation. This is also in the same directory as... (10 Replies)
Discussion started by: bhaire
10 Replies
7. Shell Programming and Scripting
Hi
I am a novice Linux/Perl user and am struggling to overcome what I am sure is a simple problem.
I am using a perl program to create a shell script daily containing between 10 and 30 "at -f" commands for the same day. Then I change the file attributes to allow the file to be executed. When... (2 Replies)
Discussion started by: simoncjones
2 Replies
8. AIX
Good morning everybody. I have just receiedv a complaint from our DBA saying that if he create a scripts to run some Oracle performance scripts using crontab and the scheduling part is ok but the job is failed when I checked on /var/adm/cron/log.
I have tried his scripts using Oracle id directly... (4 Replies)
Discussion started by: kwliew999
4 Replies
9. Shell Programming and Scripting
Hi Folks,
Could you please suggest me how to run a shell script on a solaris env without using crontab. I am actually trying to write a shell script which will grep "WORD" in the logfile andd sends a email.Thanks in advance.
Thanks
Sandeep. (3 Replies)
Discussion started by: sandeep anand
3 Replies
10. Shell Programming and Scripting
Hello gurus.
I have a problem: my crontab -e is looks like this:
ORACLE_SID=bla-bla
* 21 * * * (sqlplus hotback/hotback @/oracle/backups/bla-bla/scripts/hotback/daily_hotback.sql)
0 19 * * * /oracle/backups/dev10g/scripts/exports/daily_exports.sh
0 1 * * *... (4 Replies)
Discussion started by: MarGur
4 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)