11-14-2009
Variable problem in script when using crontab
Hi, this is my first shell script. Anyway i am trying to ftp files from one machine to another. The name of the script is ifsftp_orabkp. The code is as follows:
HOST="122.122.122.22"
USER="ftp_ftp"
PASSWD="ftp.222222"
Y1=`(perl -e '@y=localtime(time());printf "%04d%02d%02d",$y[5]+1900,$y[4]+1,$y[3];')`
Y2=`(perl -e '@y=localtime(time()-86400);printf "%04d%02d%02d",$y[5]+1900,$y[4]+1,$y[3];')`
D1=$(printf "$Y1" | cut -c 3-8)
D2=$(printf "$Y2" | cut -c 3-8)
cd /exports
ftp -nv $HOST << END_SCRIPT > /home/oracle/oracle_logs/ftpout_ora.txt
quote USER $USER
quote PASS $PASSWD
prompt
cd /erdbvol1/IFS_BKPS/ora_bkp
mput *$D1*
mput *$D2*
END_SCRIPT
When I try to run it using the following it works without any problems:
./ifsftp_orabkp
However when I use crontab :
45 10 * * * /home/oracle/oracle_scripts/ifsftp_orabkp >> /home/oracle/oracle_logs/ftpora.log 2>&1
ftpora.log shows the following errors:
$ cat ftpora.log
sh: /home/oracle_scripts/ifsftp_orabkp: not found
/home/oracle/oracle_scripts/ifsftp_orabkp: syntax error at line 6: `D1=$' unexpected
/home/oracle/oracle_scripts/ifsftp_orabkp: syntax error at line 6: `D1=$' unexpected
/home/oracle/oracle_scripts/ifsftp_orabkp: syntax error at line 1: `$' unexpected
/home/oracle/oracle_scripts/ifsftp_orabkp: syntax error at line 6: `D1=$' unexpected
Please help!
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 X11R4
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have
their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.deny file in order
to use this command.
If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use
this command, or all users will be able to use this command.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). If this
option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse
crontab and that if you are running inside of su(8) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is
given.
The -l option causes the current crontab to be displayed on standard output. See the note under DEBIAN SPECIFIC below.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com> is the author of cron and original creator of this manual page. This page has also been modified for Debian by
Steve Greenland, Javier Fernandez-Sanguino and Christian Kastner.
4th Berkeley Distribution 19 April 2010 CRONTAB(1)