Crontab not recognizing the jar files

04-30-2008

Registered User

5, 0

Join Date: Apr 2008

Last Activity: 2 August 2008, 4:58 AM EDT

Posts: 5

Thanks Given: 0

Thanked 0 Times in 0 Posts

Crontab not recognizing the jar files

Hi All,
I am using crontab which execute a shell script.
In the shell script, I am executing a java program. This Java program requires the jar files.
The cron job file ' cronfile.txt ' contents:

MAILTO="raju_utla@dcis.uohyd.ernet.in"
0-59 * * * * ./cronfile.sh >> /home/rajuutla/FilesForCronJob/logFileForCron.log

The shell script( cronfile.sh ) contents :
#!/bin/bash
#check weather server prog is running or not
test=`ps aux | grep -c java\ PostgresServer`
JAVA_HOME=/opt/SDK/jdk
CLASSPATH=/home/rajuutla/pg74.jdbc3.jar:.
if [ $test -eq 1 ]
then
echo `date`
$JAVA_HOME/bin/java -classpath $CLASSPATH PostgresServer

fi

The java program 'PostgresServer' which i am executing requires the jar file
'pg74.jdbc3.jar' mentioned above.

The problem is, directly running the above shell script with out cron, I am able to get the results. But when I use the crontab to run the java program I am not able to get the results.

What may be the problem? How to resolve this problem? I am unable to find it out.
Please help me.
Thanks to All.
Raju

rajuutla

View Public Profile for rajuutla

Find all posts by rajuutla

CRON(8) System Manager's Manual CRON(8) NAME
cron - daemon to execute scheduled commands (Vixie Cron) SYNOPSIS
cron DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see crontab(5)). Cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut- ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if such exists). Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab. SEE ALSO
crontab(1), crontab(5) AUTHOR
Paul Vixie <paul@vix.com> 4th Berkeley Distribution 20 December 1993 CRON(8)

UNIX for Advanced & Expert Users