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 HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default
value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that
job's queue, or because more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it.
All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE
queuedefs(4)