07-03-2004
1. I think you misunderstood my point. So, have you tried out what I suggested and did that work for you? I think it should, otherwise it may mean you need to explicitly specify the classpath in the java command, which is tedious and I will avoid it if ever possible because, depending on the Java project, missing some Java library class paths that exist in the default classpath will render those libraries unloadable.
No, the Java classpath has not changed. Unless you explicitly specify the classpath, the default classpath used by java ALWAYS contains the current directory (.) that's why if you put a Java class that is not in any package (see Java books for "package" if you don't know what Java packages (i.e. namespaces) are and how they work) in the current directory Java can always find it because . is in the classpath. But when you run it from cron, the current directory is not where your class resides, so it cannot be found. That was the point I would like to make in my previous reply.
PATH has nothing to do with class invocation in java UNLESS you install java in non-standard locations. You can qualify java with absolute path but as you said previously it did not work either. Therefore, it seems like Java can be loaded, it just couldn't find the class. Java doesn't use PATH to do anything internally except from to load the java executable itself.
2.
To same file:
java MyClass >~/myLogfile 2>&1
To different file:
java 1>~/stdout.log 2>~/stderr.log
But if for use with cron, I recommend avoid using ~ but to use absolute paths for filenames.
Last edited by cbkihong; 07-04-2004 at 12:20 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I can see where the nohup command can come in very handy. My question is, do you have to do something like this (nohup) in order to run certain cron jobs? On the windows side, I have a couple of scripts that basically run continuously, so all I have to do is ctrl-alt-del to lock my workstation,... (2 Replies)
Discussion started by: wmosley2
2 Replies
2. Shell Programming and Scripting
I'm new to cron, What does this syntax mean?
0 5 * * 1-5 /u08/0ra33/run_arch.sh
thanks (2 Replies)
Discussion started by: ted
2 Replies
3. AIX
Could someone please tell me how I might specify in cron that I want a job to run only on the "last saturday" of the month?
Thanks. (2 Replies)
Discussion started by: DenD
2 Replies
4. UNIX for Dummies Questions & Answers
I have a script which goes out and installs a package on a box remotely and im trying to get it to add a cron job too..but im having a few problems, whilst it does add the entry it wont run unless I connect to the machine , crontab -e, then :wq. This re-reads the configuration file and it will now... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
5. Shell Programming and Scripting
Folks;
I have this script in SUN which if i run it using command line, it works fine, but when i run it using cron, it work but it misses one thing. here's the details
#!/bin/bash
cd /opt/new_script
for i in ./report*Groups.sh; do $i $1; done
This script above when runs through cron, it... (4 Replies)
Discussion started by: moe2266
4 Replies
6. Shell Programming and Scripting
folks;
This might sounds stupid, but i tried few ways to solve it without luck.
I need to run a job on the first Saturday of every month at 10 pm. so far i'm not sure what am i doing wrong, but every time i set it, it always run every Saturday instead of the first Saturday of every month.
Any... (4 Replies)
Discussion started by: moe2266
4 Replies
7. UNIX for Dummies Questions & Answers
There is this script I'd like to put into cron, but it asks for date verification. It'll prompt you to press enter to continue. Usually, 100% of the time the dates are ok, so is there a way to run this script in cron and bypass the "enter" prompt? (3 Replies)
Discussion started by: NycUnxer
3 Replies
8. Shell Programming and Scripting
Hi,
We have developed the script which will send an (html)attachment in through mail. The stand alone script is working fine ,but when we schedule it cron the "nail" command is not working that is we are not receving any mail.
Following is the command which we used to send the mail. :confused:... (4 Replies)
Discussion started by: Amey Joshi
4 Replies
9. UNIX for Dummies Questions & Answers
Hi all, hopefully someone out there can give me some tips on how to resolve this
I have a simple shell script
who -u > /tmp/userlog
one of the line stored in userlog when executing shell script manually:
jim123 pts/24 2012-03-30 13:02 00:56 4131 (xya.dsfgds.com)
one of the... (4 Replies)
Discussion started by: Linux_Novice
4 Replies
10. UNIX for Dummies Questions & Answers
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)