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 MOJAVE
crontab
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