04-10-2006
A way to debug the problem is run the script in debug mode using -x
eg ksh -x script
As script is a piece of interpreted code as the execution flows you will be able to located where the problem is.
Regards,
Rishi
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
This is the script
path=/oracle/ora10gdb/sample
archive=/oracle/ora10gdb/archive
cd $path
for i in `ls`;do
mv $i $archive
Done
Please tell me why it is givind this error (2 Replies)
Discussion started by: dineshr85
2 Replies
2. Shell Programming and Scripting
hi
i have error like this' syntax error end of file unexecpeted.and give me the example of cut command
as soon as possible: (1 Reply)
Discussion started by: naveeng.81
1 Replies
3. Shell Programming and Scripting
HI,
I was converting a .bat file to .sh file for unix
Code snippet
#!/usr/bin/sh
set -x
if then
goto RegularBuild;
CURDIR="$1";
cd "$CURDIR";
:RegularBuild
echo "Checking for existing fip_help.properties in def/properties directory..."
if then
rm -f fip_help.properties;
... (1 Reply)
Discussion started by: srisreeku
1 Replies
4. Shell Programming and Scripting
HELP PLEASE!!
I am running this script, and i keep getting the error 'end of file' unexpected. I know that usually means parenthesis or whatever is out of place but i cant find anything!! I am new to scripting and i put some "print" staements in and it is not getting past the first IF statment... (7 Replies)
Discussion started by: weatherman0516
7 Replies
5. Shell Programming and Scripting
hi,
i am trying to connect to sqlplus in an 'if block' from the script.
it is giving unexpected end of file error.
and it works fine if it is out of 'if block'.
if anybody have idea on this, can you please help me to solve the error ?
piece of code is given below.
if
then... (11 Replies)
Discussion started by: vinayakatj56
11 Replies
6. Shell Programming and Scripting
I am getting a "line 47: syntax error: unexpected end of file", why? According to my estimate, line 47 is 2 lines after the last line of code here. Also, the $1 variable represents the current user logging in, and the script runs with root privileges (This is a Mac OS login hook script using... (5 Replies)
Discussion started by: glev2005
5 Replies
7. Shell Programming and Scripting
Hi,
On adding below code to my script shows the error on executing else script works fine.
sqlplus $user_name/$password <<EOL
truncate table order;
commit;
truncate table order_hist;
commit;
insert into order(ID,TRAN,CUST_NAME,OPT_VAL) select * from order_bkp;
insert into... (5 Replies)
Discussion started by: milink
5 Replies
8. Shell Programming and Scripting
Hi ,
I am new to Unix and this is my first shell script .
I am facing "unexpected end of file error" while executing my code . tried removing blank spaces Unable to trace out the error . PLease help !!!
#!/bin/sh
echo hello
if ]
echo hi
then
var=`cat liq_table_nm.txt`
... (6 Replies)
Discussion started by: sen180185
6 Replies
9. Shell Programming and Scripting
Hi guys,
I am new to BASH scripting and I was wondering if anyone could have a look at this code and explain to me why I am getting an Unexpected End of File Error ?
If you can that would be great / much appreciated! THANKS!
#!/bin/bash
USER=""
PASS=""
if ; then echo "You need to set... (1 Reply)
Discussion started by: spooke
1 Replies
10. Shell Programming and Scripting
I dont know where I missed the double quotes .:wall:pls review this code and help me out .
m1: line 26: unexpected EOF while looking for matching `"'
m1: line 34: syntax error: unexpected end of file
echo "script is created by prabhu Kumar ";
echo "changing the directory to wes... (2 Replies)
Discussion started by: ptappeta
2 Replies
LEARN ABOUT CENTOS
btraceback
BTRACEBACK(1) Network backup, recovery and verification BTRACEBACK(1)
NAME
btraceback - wrapper script around gdb and bsmtp
SYNOPSIS
btraceback /path/to/binary pid
DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes.
USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur-
rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below).
NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be
available in the $PATH.
If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi-
leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon.
Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the
same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse-
quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem.
ENVIRONMENT
btracback relies on $PATH to find the debugger.
FILES
/usr/lib/bacula/btraceback
The script itself.
/usr/sbin/btraceback
symbolic link to /usr/lib/bacula/btraceback
/etc/bacula/scripts/btraceback.gdb
the GDB command batch used to output a stack trace
AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org>
SEE ALSO
bsmtp(1)
Kern Sibbald 6 December 2009 BTRACEBACK(1)