I pasted the quoted code into a file and ran it and - to my surprise - it worked. I would have expected this:
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:
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.
I hope this helps.
bakunin
I just wanted to acknowledge your post bakunin. I'm not at a machine now but I'd like to not that when you say, 'sleep 10 was interrupted', that makes sense.
i am familiar with the += accumulator from Java, and haven't tried this syntax yet. So I consider this a step in the positive direction. In addition, I haven't tried XTerm yet either. I have my fingers crossed that this will make a difference. I'm really a hardware guy and in my experience, this is is a display issue. I think that my instructor, you, and myself agree that this has something to do with the way I'm setup, and a possibility of doing this in a virtual environment.
I thought I was doing myself a favor by running VirtualBox so that I could have a couple of Linux distributions and Windows Server 2008 r2 running all under the same umbrella. I haven't tried an actual install yet becuase I just didn't have time, and that's really the next step, besides trying to talk it out here.
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
snmptrapfmt
SNMPTRAPFMT(8) System Manager's Manual SNMPTRAPFMT(8)NAME
snmptrapfmt - Receive and log SNMP trap messages from a trap handler.
SYNOPSIS
snmptrapfmt [-d num] [-D] [-f cfgfile]
DESCRIPTION
Snmptrapfmt receives SNMP trap data through a local pipe. The trap data is written to this pipe by a SNMP trap handler which is called by
snmptrapd (configuration is done in /etc/snmp/snmptrapd.conf) during the installation if this package. Snmptrapfmt formats the received
trap data according to the specifications in the configuration file /etc/snmp/snmptrapfmt.conf (see this file for the syntax). The output
of the snmptrapfmt application may be written to a log file or forwarded to the syslog daemon.
The option -d 1 should be specified to enable tracing. Trace information is then written to the file /var/tmp/snmptrapfmt.trc.
If the option -f cfgfile is given, the output of the daemon is configured via the mentioned configuration file. If this option is not spec-
ified, a default output format is used.
If the option -D is given, the the program will daemonize into the background.
The syntax of the configuration file is explained in /etc/snmp/snmptrapfmt.conf !
FILES
/etc/init.d/snmptrapfmt is the start/stop script.
/etc/snmp/snmptrapfmt.conf is the configuration file.
/var/run/snmptrapfmt.pid is the PID file.
/etc/snmp/snmptrapd.conf is the configuration file of the snmptrapd daemon, which calls the trap handler snmptrapfmthdlr.
/usr/sbin/snmptrapfmt is the executable of the application.
/usr/sbin/snmptrapfmthdlr is the executable of the trap handler.
/var/run/snmptrapfmt.p is the communication pipe between the trap handler snmptrapfmthdlr and the formatter snmptrapfmt.
/var/tmp/snmptrapfmt.trc is the trace file if the option -d is specified.
/var/log/snmptrapfmt.log is the log file as specified in the configuration file.
SEE ALSO snmptrapfmthdlr(8), syslog(8), variables(5), RFC 1155, RFC 1156, RFC 1157, SNMP Security Internet Drafts
4th Berkeley Distribution 19 DECEMBER 2002 SNMPTRAPFMT(8)