#! /bin/bash
count=1
trap " echo 'I have trapped CTRL-C'" SIGTERM SIGINT
echo "Start of the program..."
while [ $count -lt 10 ]
do
echo "Loop #$count"
sleep 10
count=$[ count + 1]
done
echo "End of the program..."
I pasted the quoted code into a file and ran it and - to my surprise - it worked. I would have expected this:
Code:
count=$[ count + 1]
to caue problems, it "just doesn't seem right", but then, i use Korn Shell most of the times and avoid bash like the plague. I would have written:
Code:
(( count += 1 ))
which should do the same and is POSIXly correct (notice the spaces around "((" and "))", they are necessary), but: never argue with success, yours obviously works.
One thing i noticed, though, was: as soon as i pressed "CTRL-C" the trap was executed but the "sleep 10" was interrupted and then skipped. Pressing CTRL-C often enough let me get through with the script in less than half a minute, whereas 10x 10 seconds of sleeping should have taken 1min 40sec (plus some for the rest).
So, probably there is something with your setup. I have no idea what that would be, though. I tried in an XTerm on Fedora without any real changes and it worked as expected.
My problem is this:
I need to have a catch-all for my processes. An example would be, using a trap, in the parent, to catch any non-0 exit or invalid command (a way to catch core dumps would be cool, too) in not only the parent, but it's children and they're children. Not only that, but I also... (7 Replies)
Hello all,
I'm hoping to get a little insight from some of the wily veterans amongst you.
I've written a script to check for new outgoing files to our vendors located on our ssl server. It seems to be working ok, but the final question here, will be one of logic, and/or a better way to... (4 Replies)
Hi
Our problem is knowing:
What is the "best" way of simulating a TRAP for ERR within a function, since we know this will not work directly with ksh93 and aix5. How can we save the error encountered in the function and then deal with it in the calling script?
Thanks! (3 Replies)
Hi All
"Identify the behavior of traps, mechanism to implement traps in the snmp framework"
What does it mean?? Can anybody explain.. Whats this Trap??
Thanx in Advance. (1 Reply)
I have a script
#!/bin/ksh
trap cleanup 20
cleanup()
{
cat $t.log
echo Caught
exit 1
}
if ;then
echo Found >>t.log
exit 20
else
echo Not found >>t.log
exit 20
fi (5 Replies)
Hi folks,
I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:....
The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Hi
At the beginning of my script, i will create a file and at the end of the script i will delete that.
But i got to delete the file even if the process is forcefully killed, or server is rebooted...
I think i can make use of trap signal, but couldnt figure out how and where to use in my... (4 Replies)
First time trying to work with signals in Perl.
Reviewing example I try it, but not able to get it work for 'exit'.
I hope, I am correct, assuming, that the ending any code by
exit $return_code;
the $SIG{EXIT} should be de-referenced and processed?!
So, I have such code, that, I assume,... (5 Replies)
Discussion started by: alex_5161
5 Replies
LEARN ABOUT DEBIAN
tping
TPING(1) LAM COMMANDS TPING(1)NAME
tping - Send echo messages to LAM nodes.
SYNOPSIS
tping [-hv] [-c count] [-d delay] [-l length] nodes
OPTIONS -h Print the command help menu.
-v Turn OFF verbose mode.
-c count Send count messages.
-d delay Delay delay seconds between each message.
-l length Each message is length bytes long.
DESCRIPTION
The tping command sends messages to, and collects replies from, a list of nodes, via the LAM echo server. It is similar to the UNIX
ping(8) command, and is used as a quick diagnosis of the LAM network.
Unless options are specified, tping sends a 1 byte message an infinite number of times, displaying the roundtrip time of each message as it
completes, with a delay of 1 second between roundtrips. After the loop is broken (with keyboard interrupt, eg: ^C), tping prints statis-
tics about all roundtrip messages.
EXAMPLES
tping h
Echo messages to the local node.
tping -v n7 -l 1000 -c 10
Echo 1000 byte messages to node 7. Stay silent while working. Stop after 10 roundtrips and report statistics.
BUGS
There is no built-in timeout and tping will wait forever to receive an echo. If no echo is received, due to a dead link or node, tping
hangs. Stop the process with a keyboard suspend signal (eg: ^Z) and terminate LAM with lamhalt(1) or lamwipe(1) (although the use of
lamwipe(1) is deprecated).
SEE ALSO lamhalt(1), lamwipe(1)LAM 7.1.4 July, 2007 TPING(1)