I hv a crontab job (script) that can be run normally , now I try to run it on the shell but can't be run , can advise what is difference between run a script on crontab and run it manually ? is it the difference of system enviornment ?thx
I tried to fix it by below method ,
I write a script... (3 Replies)
Hello,
Every evening I run few shell scripts on AIX Production Box, One shell script takes about one hour to complete and does some DB updation and application processing etc. The shell scripts are getting launched from prompt and not through cron or any scheduler as they require some manual... (0 Replies)
is it possible to soecify time overnight in 5 days for example:
0 18-7 * * 1-5 /mycode
is this okay to use 18-7 because im not getting the results correctly? (4 Replies)
Hello everybody,
Can anybody tell me how do we comfirm the execution of a scheduled job ?
In other words, how do I know whether my scheduled script is being executed or not ?
Thanks
Jitu JK (2 Replies)
Hi,
I want to run a crontab job on solaris 10.5. I have configured the crontab accordingly
10 * * * * /scripts/dbalter.pl >> /scripts/cronout.txt
However this does not work .Then I go to /var/mail/root and find an error in the output:
From root@myserver Wed Feb 4 17:02:00 2009... (1 Reply)
Hi All,
At present I am using a UNIX Script which is running a set of JOBS. These JOBS are to be repeated for 20 times, means the same set of JOBS are repeated by just passing different arguments (From 1 to 20).
Is there any way by which I can execute them parallel?
At present its all... (4 Replies)
Hi
I have shell script to excute the SQL script.And i have scheduled those shell script in crontab.But the Shell script is not running timely and i got the below error
Crontab entry
15 05 17 7 * /export/home/vcpsapp/vcps/stat.sh
Output
Your "cron" job on uspxivus16... (3 Replies)
Dear All.
I have a scripts which does many task like house keeping, moving file to different location and loading the data into oracle.
I run this scripts daliy manually , I decided to put it into cron. I have put the scripts into crantab but the behaviour of the scripts have changed. it... (2 Replies)
Hi Guys,
I need help to clear my doubt w.r.t Crontab execution.
uname -a
HP-UX myservername B.11.31 U ia64 1422528451 unlimited-user licenseI created a crontab entry to execute particular job on Saturday 11/15/2014 11:22
Below is the cron entry
#refresh DEVDB from PRODDB
22 11 15 11 6... (6 Replies)
HI,
I have written an executable file in unix and I was able to execute it successfully but when I called this file with cron job it was giving error like "permission denied" and "No such file or directory".
Please help in how cron calls the file and what permission is required on the file... (2 Replies)
Discussion started by: vipin kumar rai
2 Replies
LEARN ABOUT OPENDARWIN
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab 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 though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/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.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). If this
option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse
crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake.
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 -l option causes the current crontab to be displayed on standard output. See the note under DEBIAN SPECIFIC below.
The -r option causes the current crontab to be removed.
The -e option is used to edit 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. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO crontab(5), cron(8)FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
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
A fairly informative usage message appears if you run it with a bad command line.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com> is the author of cron and original creator of this manual page. This page has also been modified for Debian by
Steve Greenland, Javier Fernandez-Sanguino and Christian Kastner.
4th Berkeley Distribution 19 April 2010 CRONTAB(1)