11-14-2009
Echo your env in your script and have it run from cron.
So put this at the beginning of your script
env > /tmp/env
Have that run from cron, and then post the results. This is a simple way to trouble shoot enviornment variable problems. You can compare to how its running from cron, from when you're executing it yourself.
10 More Discussions You Might Find Interesting
1. Solaris
Hi Experts,
Am facing some problems with script (Sun solaris 9). My script (sqlplus.sh)looks like this. . .
...............................................
set 'date'
dd=$3
export dd
mon=$2
export mon
yyyy=$6
export yyyy
cd /oracle/P47/saparch... (8 Replies)
Discussion started by: vrjalli
8 Replies
2. Linux
Crontab:
16 14 * * * /root/bin/./empty_mail.sh >> /root/bin/log.txt
L=`mailq |grep -c frozen`
echo "${NUMMAIL} frozen mail to be removed from the mailq"
#echo "Press Enter to continue"
#read CONTINUE
echo -en "-> "
for i in `mailq | grep frozen | awk '{print $3}'` ; do
exim4 -Mrm $i... (1 Reply)
Discussion started by: wessberg
1 Replies
3. Shell Programming and Scripting
I am trying to use the CRON utility in Fedora 11 & CentOS...
I intend to run a script which pops up a warning message every hour and i made the following entry using "CRONTAB -e "
* * * * * sh /bin/myscript.sh
But this does not seem to be running.
Another thing to note is that,... (4 Replies)
Discussion started by: Vabiosis
4 Replies
4. Shell Programming and Scripting
There are two files one is shell script (sample.sh) and another is configuration file (sampl_conf.cfg)
configuration file contains one variable $FTP_HOME. the value of this variable vaires for user to user. If user is say jadoo then value is /home/jadoo/ftp/, for user1 - /home/user1/ftp. The... (0 Replies)
Discussion started by: jadoo_c2
0 Replies
5. Shell Programming and Scripting
Please help me on below..
https://www.unix.com/shell-programming-scripting/141533-retrieve-value-environment-variable-shell-script-called-crontab.html#post302442024
I'm still here. I can still see you! (0 Replies)
Discussion started by: jadoo_c2
0 Replies
6. UNIX for Dummies Questions & Answers
There are two files one is shell script (sample.sh) and another is configuration file (sampl_conf.cfg)
configuration file contains one variable $FTP_HOME. the value of this variable vaires for user to user. If user is say jadoo then value is /home/jadoo/ftp/, for user1 - /home/user1/ftp. The... (4 Replies)
Discussion started by: jadoo_c2
4 Replies
7. HP-UX
I have a script scheduled in cron as shown below.
16 12 * * * /users/mydir/bin/process_master.ksh `date '+%Y%m%d'` >> /users/mydir/process_master.out
This script executes correctly when invoked on command line, but doesn't work the same when scheduled in crontab. Crontab is working fine... (3 Replies)
Discussion started by: mk1216
3 Replies
8. Shell Programming and Scripting
Hi everybody,
I have a perl script. I want to run it as a cron job every 10 minutes. I insert the command into crontab , using crontab -e.
The problem is, I didnt get any output from script inside crontab, whereas when I run it manually through 'perl myscript.pl' it running well. Here is the cron... (2 Replies)
Discussion started by: franzramadhan
2 Replies
9. UNIX for Dummies Questions & Answers
Hi guys,
I have a shell script which i have put on crontab to run every min. Problem is that is isn't running.
But if i run the script from the existing location it runs perfectly.
but if i got out of the directory and run it giving the path. it doesn't work.
sh script_name.sh ----... (3 Replies)
Discussion started by: nick1982
3 Replies
10. Solaris
Hi guys!
I created a backup script that works fine when I run manually, but when I put a crontab job to execute it the result are not the expected. (not a time problem).
Here is my script:
bash-3.00# cat /bk_tool/backup2.sh
#!/usr/bin/csh
clear
set DIR_HOST='SCP08'
... (3 Replies)
Discussion started by: andredemartini
3 Replies
LEARN ABOUT OPENSOLARIS
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. 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 the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1 A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) 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 nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.11 1 Mar 1994 queuedefs(4)