That is understandable. You try to set an environment, but you start two separate environments for this. In one of them you source in the file /etc/profile.sas:
If this command returns "TRUE" (or 0, which is, for this purpose, the same), then in a second environement the command
is executed. But perhaps you rely on a certain environment to be set inside your script, not in some other unrelated process. This is why your script (most probably) failed.
Note that this is all conjecture because i cannot read what in the script /data/work/cr_folder1.sh is (crystal ball not working, y'know).
If my educated guesswork is indeed right you might want to do it this way:
Hi all ,
When i am tryting to execute crontab from home directory for a shell script which is located in some directory it is giving a error message
The crontab file is
0 9-17 * * 1-5 /mydir/myshell
The following output is given
Your "cron" job
/mydir/myshell
produced the following... (1 Reply)
Dear Friends,
I have tried to fire a job on daily basis through crontab command but it willn't work.
i have given in the following manner:
07 19 * * * exp /user_name/passwd/ file = /path/file-name full = N owner = user-name
but it is giving error that permission denied.
i have checked that... (8 Replies)
Hi All,
There is a requirement to create a file everyday using the cronjob with the date as its name.
any suggestions for the crontab command that'll serve this purpose?
e.g.
02 30 * * * touch abcd.`date +%d.%m.%y`
needless to say.. this doesn't work..
looking fwd to lots of... (7 Replies)
hi I am trying to activate auto_run.sh from crontab using following command line but nothing happen.
35 11 * * * -exec /u/uniacc/auto_run.sh
and this is the first line of auto_run.sh
ksh exec auto_inv.4ge > kti (4 Replies)
Hi all you enlightened unix people,
I've been trying to execute a perl script that contains the following line within backticks:
`grep -f patternfile.txt otherfile.txt`;It takes normally 2 minutes to execute this command from the bash shell by hand.
I noticed that when i run this command... (2 Replies)
Dear All,
We wrote a script to clean email mailbox when they're nearly full and put it in cron :
0 0 * * * /root/quota/autoclean.sh > /root/quota/autoclean.`date '+%Y%m%d'` 2>&1
I've run this command from command prompt, it did work.
However, if running from cron, it returned such error... (1 Reply)
Hello Experts,
I am facing problem in date command with TZ
test.sh
Output : 26-May-2010 27-May-2010
I scheduled this script everyday at 1 a.m
00 01 * * * sh test.sh
when i was called this script test.sh from crontab , it was giving me other output (1 Reply)
Hi Expert,
I am using TZ for extracting yesterday date and day before yesterday date
example :
date_yes=`TZ="GMT+28" date +'%d-%b-%Y'`
date_dbyes=`TZ="GMT+48" date +'%d-%b-%Y'`
echo $date_yes $date_dbyes
26-May-2010 27-May-2010
I have written a small script for the same named... (1 Reply)
Dear Friends,
I am trying to copy SAP log file from one HPux server1 to another HPux server2 remotely through one script.
following command has written in the script.
rcp -rp /oracle/PRD/sapreorg/*.dbf oraprd@drsite:/oracle/PRD/sapreorg
Above command working fine from command mode.... (5 Replies)
Hi All,
I want a script to run every 5 minutes and in the command prompt i typed the following command
$ */5 * * * * /u01/EnvironmentStartup/validateservices.sh
and when i enter i'm getting a message
"-bash */5: No such file or directory"
Any ideas please?
Thanks
Please wrap all code,... (6 Replies)
Discussion started by: thinkingeye
6 Replies
LEARN ABOUT CENTOS
crontab
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)