03-25-2010
The environment in cron isn't the same as your interactive environment. The error tells you as much: the variable AUTOSYS is not set (and probably others.) You will have to import the required environment variables into the script you run from cron.
You can do "printenv" from your interactive ksh session and from a cron script to compare the environment.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am running a script by scheduling it using the cron. The line in the cron file is -
10 * * * * ksh -v /apps/gofis/svam/cos_automation/cos_automation.sh vpqa > /apps/gofis/svam/cos_automation/cron.log 2>&1
But after the job is executed, the cron.log contains some part from... (4 Replies)
Discussion started by: ankurgupta
4 Replies
2. Shell Programming and Scripting
I have the following script (trapsize) that checks a file size on my syslog server, and if the file is gt 6g, it will mail an alert to the admin for inspection. The following works like a champ when I execute ./trapsize logged in as root user using bash shell.
FILESIZE=$(ls -l /opt2/fwsm/fwsm... (3 Replies)
Discussion started by: altamaha
3 Replies
3. Shell Programming and Scripting
Hi All,
When i am runing a script from home directory the output is fine, but whenever i am running a script from any of the directory the output is fine while a "Blank file" is created named as "1" in the particular directory.
Will you please suggest any options to fix this problem. It... (1 Reply)
Discussion started by: r_jha17
1 Replies
4. Shell Programming and Scripting
#!/bin/ksh
file="/pkgs/roots/scripts/ISQL_op.txt"
isql -H 11.11.11.111:1111 -U myUser -P myPwd -o $file << eof
go
select * from Table1
go
eof
my cron entry
00 08 03 11 * /pkgs/roots/scripts/testc.ksh
file permission of the script is correct, i have used absolute path everywhere.
... (2 Replies)
Discussion started by: vikram3.r
2 Replies
5. Solaris
Hi,
I''ve made a script that's running fine from the command line but when running from cron it encounters the following issue:
/tmp/tstscript/testfail.ksh: typeset: not found
I've searched in Google and couldn't find anything, here's the beggining of the script (I can post the rest if... (4 Replies)
Discussion started by: Cvg
4 Replies
6. Shell Programming and Scripting
Hello All,
I am running the below script.when i am running from shell or terminal its running fine but running using cron its not working.
################################
b36376 27 % cat make_nis_account_ankit.sh
#!/bin/ksh
... (2 Replies)
Discussion started by: ajaincv
2 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am running a script thorugh cron which is given below.
this script is not doing its defined job through cron ,files are still in unzipped state.
But when i run this script as ./script.sh it gets executed fine and does all that is required.
also when i run thi script as sh... (2 Replies)
Discussion started by: Jcpratap
2 Replies
8. Shell Programming and Scripting
Hi All,
I am running the below shell script through cron and surprisingly it gives different output
$uname -a
Linux 2.6.18-194.3.1.7.3.el5xen #1 SMP Fri Jul 30 00:08:45 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ echo $SHELL
/bin/bash
shell script:
cat sar_cpu.sh
#!/bin/bash
... (10 Replies)
Discussion started by: a1_win
10 Replies
9. Shell Programming and Scripting
Hi All,
I have a script which is running fine while triggered manually, However if I placed
in crontab it throwing an error.
#!/usr/bin/ksh
set -vx
lc=1
st_date=$(`date "+%Y%m%d"`)
LOGFILE=/home/transfer.log.$st_date
file="/home/OM_WF.log.$st_date"
Manual run -
lc=1
+ lc=1... (4 Replies)
Discussion started by: nag_sathi
4 Replies
10. UNIX for Beginners Questions & Answers
I have prepared script to get the file details everyday and send mail. while running bash script manually , it sends output in body . but does not send through cron.
cron sends only subject . I believe have to use some wait or sleep syntex. to complete first . please help.
#!/bin/bash
ls... (10 Replies)
Discussion started by: yash_message
10 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