07-19-2016
You need to remove the # from in front of the export to actually change your PATH. As is, cron will be running it with a very minimal path.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wrote a script using 'expect' tool to change the password of my login id, every fortnight. And I had put it as a cron job.
The cron job is throwing an error
ld.so.1: /usr/local/bin/expect: fatal: libtcl8.3.so: open failed: No such file or directory
The environment variables are set... (4 Replies)
Discussion started by: Deepa
4 Replies
2. HP-UX
This isn't the usual problem that a shell script runs from the command line and not the cron. It's a little different.
Among other things, the shell scrip executes my .profile to set a bunch of variables. It then does an env to ensure that it ran OK.
There are echos in the shell script and... (2 Replies)
Discussion started by: abNORMal
2 Replies
3. Shell Programming and Scripting
My searches turned up nothing relevant, so I apologize if this has already been looked at.
I am trying to run an expect script from a Solaris machine, that ssh's into an AIX machine, and interacts with a SMIT created menu system that runs a few backups for me.
The expect script runs fine when... (0 Replies)
Discussion started by: Mariognarly
0 Replies
4. Shell Programming and Scripting
Hi Gurus,
I am new to scripting and needs your help in expect script used for telnet. I wrote a simple script as
#!/usr/bin/expect-5.43 -f
spawn telnet localhost 2233
expect "password:"
send "secret\r"
send "i data.cnbc.com\r"
send "exit\r"
expect eof
When I am trying to execute... (2 Replies)
Discussion started by: niks_yv
2 Replies
5. Shell Programming and Scripting
Hi,
I have a shell script as below:
ORACLE_HOME=/usr/local/opt/oracle/product/dev
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME/bin:/usr/bin
export PATH
OUTFILE=/export/home/`basename $0`.out
export OUTFILE
export IDEN
df -k . | tail -1 | read a b c d e f
echo $a >> $OUTFILE
echo $b... (4 Replies)
Discussion started by: Abhinav Pandey
4 Replies
6. Shell Programming and Scripting
Hi have a script which transferers from Microsoft server to Linux box.
The scripts(ksh) is on Linux box.
If I run script from terminal, it transfers files to directory. Where as If
I run script from CRON. It does not.
Here is the log of both:
Terminal execution log:... (2 Replies)
Discussion started by: dipeshvshah
2 Replies
7. UNIX for Dummies Questions & Answers
I'm trying to learn how to use cron for repetative tasks. I have an external disk that needs to be unmounted and remounted every hour due to some problems that a backup utility (specifically, TimeMachine) is having repeatedly accessing the device. I've created a shell script that will find the... (3 Replies)
Discussion started by: illuminate
3 Replies
8. Shell Programming and Scripting
Hi,
I created a script which connects to database and update a table.
This script is running fine when i run it manually but when i am trying to execute it scheduling in crontab.script is executing but Data is not getting updated.
below is my script
sqlplus test/##### >> test_feed.log <<!... (6 Replies)
Discussion started by: sv0081493
6 Replies
9. Shell Programming and Scripting
My cron file. Copied $PATH
# Minute Hour Day of Month Month Day of Week Command
SHELL=/bin/ksh
PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/perl/lib:/perl/lib/lib/perl5:/perl/scripts:.:/perl/lib/local:/home/popeye:/temp
0... (3 Replies)
Discussion started by: popeye
3 Replies
10. AIX
Hi,
I have a shell script which fetches the MRP status and the LAG status.
When I execute it manually like, sh <script_name>, it fetches the output as expected, but when I schedule through crontab, it's not working as expected.
Any help would be really appreciated.
Here is the code... (3 Replies)
Discussion started by: Nagaraj R
3 Replies
cron(8) System Manager's Manual cron(8)
NAME
cron - The system clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
The cron daemon runs shell commands at specified dates and times. Commands that are to run according to a regular or periodic schedule are
found within the crontab files. Commands that are to run once only are found within the at files. You submit crontab and at file entries
by using the crontab and at commands. Because the cron process exits only when killed or when the system stops, only one cron daemon
should exist on the system at any given time. Normally, you start the cron daemon from within a run command file.
During process initialization and when cron detects a change, it examines the crontab and at files. This strategy reduces the overhead of
checking for new or changed files at regularly scheduled intervals. The cron command creates a log of its activities. The cron daemon
must be started from the system startup scripts because it must begin execution without a login user ID set. The cron daemon starts each
job with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective
and real group IDs Supplementary groups
It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok-
ing process: Audit control and disposition masks Kernel authorizations
DIAGNOSTICS
The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID.
FILES
Specifies the command path. Main cron directory Directory containing the crontab files. List of allowed users. List of denied users His-
tory information for cron Queue description file for at, batch, and cron
RELATED INFORMATION
Commands: at(1), crontab(1), rc0(8), rc2(8), rc3(8)
Files: queuedefs(4) delim off
cron(8)