07-10-2012
So there is no way I could trap the error from the while loop?
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi folks a wee problem that requires some help.
I am writing a script that allows me to automate the changing of a password in sqlplus
the problem i encounter is that the code contains a case statement that allows the helpdesk to select whether to allow or deny access by switching the... (1 Reply)
Discussion started by: w33man
1 Replies
2. Shell Programming and Scripting
Hi,
example of Unix / Linux dialog utility is below.
I am going to use dialog as simple GUI for testing of a modem.
So I need to combine some dialog boxes into one.
I need to have input box, output box, info box, dialog box,
radiobox as in any standard program with graphical user... (2 Replies)
Discussion started by: jack2
2 Replies
3. Shell Programming and Scripting
I wrote a script to capture some rows from the DB.
However I want to capture the errors if the DB instance is down which usually produces errors like below. What should be my approach to kill script if the DB instance is down:
DATABASE ERRORS:
Msg 937, Level 14, State 1:
Server... (2 Replies)
Discussion started by: moe458
2 Replies
4. UNIX for Dummies Questions & Answers
Hi
I am trying to fetch the data from Oracle Table
More my_query.sql | sqlplus -s 'scott/tiger@OrcaleSID ' | sed 's///g;s///g' > sample_file
Now if the table passed in the my_query.sql is wrong or there is some other error insied SQL how i can caputure that
i tried
More... (1 Reply)
Discussion started by: max_hammer
1 Replies
5. UNIX for Dummies Questions & Answers
Google is not helpful here.
It is probably trivial but I can't get my head around it.
How do I capture an error which crashes out due to say a syntax error to a file?
(Note that I manually reset error.log to zero length.)
Consider this junk code:-
#!/bin/sh
# Launch as ./trap.sh... (2 Replies)
Discussion started by: wisecracker
2 Replies
6. UNIX for Dummies Questions & Answers
HI Team ,
Is there a way to capture information logs ( session or workflow ) and grep only ERROR or FAIL messages and send to email distro
using mailx or sendmail option.
I have around 200 sessions running on daily basis and this script has to run every day , and capture only error... (0 Replies)
Discussion started by: Perlbaby
0 Replies
7. Shell Programming and Scripting
Hello Everyone,
I have written a file validation script in unix to compare the data and trigger file.My requirement is if the file validation fails,I need to upate the error details in a table
ex:Below is the one of many validation checks i am doing
if
then
echo "Actual count between... (3 Replies)
Discussion started by: karthik adiga
3 Replies
8. Shell Programming and Scripting
Hi everyone , i am trying to do a shell script with dialog , but i have a problem capturing each input variable to then use "echo" to write those inputs on specific orders in a file .
If i use this code :
dialog --backtitle "Dialog Form Example" --title "Dialog - Form" \
--form "\nDialog... (1 Reply)
Discussion started by: pedropt
1 Replies
9. Shell Programming and Scripting
Hi,
I have a script that runs a tar command to standard out then pipes to a gzip:
tar cfE - * | gzip -c > OUT.gz
At the moment, even if the tar fails (e.g. because of lack of disk space), the gzip still runs successfully.
Is there a way to make the whole line exit with a non-zero error... (6 Replies)
Discussion started by: Catullus
6 Replies
trap(1) User Commands trap(1)
NAME
trap, onintr - shell built-in functions to respond to (hardware) signals
SYNOPSIS
sh
trap [ argument n [n2...]]
csh
onintr [-| label]
ksh
*trap [ arg sig [ sig2...]]
DESCRIPTION
sh
The trap command argument is to be read and executed when the shell receives numeric or symbolic signal(s) (n). (Note: argument is scanned
once when the trap is set and once when the trap is taken.) Trap commands are executed in order of signal number or corresponding symbolic
names. Any attempt to set a trap on a signal that was ignored on entry to the current shell is ineffective. An attempt to trap on signal 11
(memory fault) produces an error. If argument is absent all trap(s) n are reset to their original values. If argument is the null string
this signal is ignored by the shell and by the commands it invokes. If n is 0 the command argument is executed on exit from the shell. The
trap command with no arguments prints a list of commands associated with each signal number.
csh
onintr controls the action of the shell on interrupts. With no arguments, onintr restores the default action of the shell on interrupts.
(The shell terminates shell scripts and returns to the terminal command input level). With the - argument, the shell ignores all inter-
rupts. With a label argument, the shell executes a goto label when an interrupt is received or a child process terminates because it was
interrupted.
ksh
trap uses arg as a command to be read and executed when the shell receives signal(s) sig. (Note that arg is scanned once when the trap is
set and once when the trap is taken.) Each sig can be given as a number or as the name of the signal. trap commands are executed in order
of signal number. Any attempt to set a trap on a signal that was ignored on entry to the current shell is ineffective. If arg is omitted
or is -, then the trap(s) for each sig are reset to their original values. If arg is the null (the empty string, e.g., "" ) string then
this signal is ignored by the shell and by the commands it invokes. If sig is ERR then arg will be executed whenever a command has a non-
zero exit status. If sig is DEBUG then arg will be executed after each command. If sig is 0 or EXIT for a trap set outside any function
then the command arg is executed on exit from the shell. The trap command with no arguments prints a list of commands associated with each
signal number.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
csh(1), exit(1), ksh(1), sh(1), attributes(5)
SunOS 5.10 23 Oct 1994 trap(1)