12-06-2011
I would say its not a good idea to use the same name for a variable and a file when you use both in the same script... (For me it was already confusing...) Then of course there is this syntax error: a while expects straight after a "do".... So try your script again and use capital letters for your variables (after placing correctly the "do"). Does it work?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
i wrote a while script as part of a huge program. this script, once picked, begins to output data to the person using it. pretty easy, as the person doesn't have to keep typing commands to get the output that the while loop automatically throws out.
now, the thing is, while this while-script... (3 Replies)
Discussion started by: Terrible
3 Replies
2. Shell Programming and Scripting
im running a while loop as a file watcher, with incremental counter on the retries..however when the retries reach it's limit i want it exit and echo and error and stop the batch. Im not sure the code i have will do that already...
Here is what i have that works:
#!/usr/bin/ksh
count=0... (2 Replies)
Discussion started by: sigh2010
2 Replies
3. Shell Programming and Scripting
hi,
how to exit from "if" loop?actually i have mutliple "if" conditions, i have to exit from each "if" loop,if it is true...:confused:
Please suggest me... (3 Replies)
Discussion started by: sreelu
3 Replies
4. Shell Programming and Scripting
This code is used to check for duplicate ip and hostnames in an /etc/hosts file
CENTRAL is path to /etc/hosts
AWK =awk
#check CENTRAL for duplicate ips or hostnames#
grep -v "^#" $CENTRAL | $AWK '{ print $1, $2; }' | \
while read ip hostname
do
if... (5 Replies)
Discussion started by: trimike
5 Replies
5. Shell Programming and Scripting
Whats the wrong with the following code:
if ; then
echo "File XYZ Exist"
if ] ; then
echo "File abc is not empty, script continues"
else
echo "File abc is empty, script aborts"
exit 0
fi
else
echo "File XYZ does not exist"
exit 0
Error: testscript.ksh:... (3 Replies)
Discussion started by: karumudi7
3 Replies
6. HP-UX
Hello;
Am experiencing odd problem with ssh:
=========
ssh -vvv remote_host
:
:
debug2: channel 0: rcvd adjust 65536
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0... (4 Replies)
Discussion started by: delphys
4 Replies
7. Emergency UNIX and Linux Support
Below for loop not exiting. Can someone help?
JBOSS_INST_ARGS=01 02
if ; then
for i in $JBOSS_INST_ARGS; do
/u/jboss-6.1.0.Final/bin/jboss_init_wise$i.sh start;
done (8 Replies)
Discussion started by: vino_hymi
8 Replies
8. Shell Programming and Scripting
Hi all,
Please guide me writing this script
Follwing is the file which I have created, which contains the files to be copied.
cat system1-dr.txt
/etc/passwd
/etc/shadow
/etc/group
/etc/vfstab
/etc/profile
/etc/default/init
/etc/shells
/etc/dfs/dfstab
/etc/dfs/sharetab... (11 Replies)
Discussion started by: manalisharmabe
11 Replies
9. Shell Programming and Scripting
Dear all,
We have a service that we start up remotely with rsh but unfortunately, the rsh never returns to the calling server. This seems to be because the processes of the service we've just started hold the port open.RBATTE1 @ /home/RBATTE1>netstat -na|grep 49.51
tcp4 0 0 ... (1 Reply)
Discussion started by: rbatte1
1 Replies
10. Shell Programming and Scripting
Hi all,
I am calling a subroutine which checks if a log file is writeable and if not, prints something stdout and also log something into the same file, which doesn't work neither of course.
Anyway, there is enough exit() calls, that should stop it working, but the problem is, that I get the... (5 Replies)
Discussion started by: zaxxon
5 Replies
LEARN ABOUT OPENSOLARIS
catch
catch(1T) Tcl Built-In Commands catch(1T)
__________________________________________________________________________________________________________________________________________________
NAME
catch - Evaluate script and trap exceptional returns
SYNOPSIS
catch script ?varName?
_________________________________________________________________
DESCRIPTION
The catch command may be used to prevent errors from aborting command interpretation. The catch command calls the Tcl interpreter recur-
sively to execute script, and always returns without raising an error, regardless of any errors that might occur while executing script.
If script raises an error, catch will return a non-zero integer value corresponding to the exceptional return code returned by evaluation
of script. Tcl defines the normal return code from script evaluation to be zero(0), or TCL_OK. Tcl also defines four exceptional return
codes: 1 (TCL_ERROR), 2 (TCL_RETURN), 3 (TCL_BREAK), and 4 (TCL_CONTINUE). Errors during evaluation of a script are indicated by a return
code of TCL_ERROR. The other exceptional return codes are returned by the return, break, and continue commands and in other special situa-
tions as documented. Tcl packages can define new commands that return other integer values as return codes as well, and scripts that make
use of the return -code command can also have return codes other than the five defined by Tcl.
If the varName argument is given, then the variable it names is set to the result of the script evaluation. When the return code from the
script is 1 (TCL_ERROR), the value stored in varName is an error message. When the return code from the script is 0 (TCL_OK), the value
stored in resultVarName is the value returned from script.
If script does not raise an error, catch will return 0 (TCL_OK) and set the variable to the value returned from script.
Note that catch catches all exceptions, including those generated by break and continue as well as errors. The only errors that are not
caught are syntax errors found when the script is compiled. This is because the catch command only catches errors during runtime. When
the catch statement is compiled, the script is compiled as well and any syntax errors will generate a Tcl error.
EXAMPLES
The catch command may be used in an if to branch based on the success of a script.
if { [catch {open $someFile w} fid] } {
puts stderr "Could not open $someFile for writing
$fid"
exit 1
}
The catch command will not catch compiled syntax errors. The first time proc foo is called, the body will be compiled and a Tcl error will
be generated.
proc foo {} {
catch {expr {1 +- }}
}
SEE ALSO
break(1T), continue(1T), error(1T), return(1T), tclvars(1T)
KEYWORDS
catch, error
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------+-----------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-----------------+
|Availability | SUNWTcl |
+--------------------+-----------------+
|Interface Stability | Uncommitted |
+--------------------+-----------------+
NOTES
Source for Tcl is available on http://opensolaris.org.
Tcl 8.0 catch(1T)