01-30-2008
it is not working when system gets rebooted!!
this works if the main script gets killed by kill -9 or CTRL-C ......... but if system gets rebooted while the script is running ..... and during this interruption no mail is sent to us. that prgramm killed or interuppted.... any idea or some work around.....?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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)
Discussion started by: marc6057
7 Replies
2. Shell Programming and Scripting
I'd like to use "trap" command on my unix machine sunOS 5.7.
But somehow when I do "which trap" command, it's no where to be found.
Any one knows how I can get it installed?
Thanks!! (9 Replies)
Discussion started by: whatisthis
9 Replies
3. Shell Programming and Scripting
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)
Discussion started by: mph
4 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: theteeth07
3 Replies
5. Shell Programming and Scripting
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)
Discussion started by: thana
5 Replies
6. Shell Programming and Scripting
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)
Discussion started by: frozensmilz
1 Replies
7. Shell Programming and Scripting
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)
Discussion started by: vasuarjula
4 Replies
8. Shell Programming and Scripting
trap "" 1 2 3
Thanks,
-dog (1 Reply)
Discussion started by: landog
1 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
That is the last reply I received from my instructor, and I'm looking for some alternatives.
When using... (2 Replies)
Discussion started by: newuser45
2 Replies
10. Shell Programming and Scripting
Hi Ppl,
Need help
$ cat trap.sh
#!/bin/bash
trap cleanup 1 2 3 15
cleanup()
{
echo “I was running \”$BASH_COMMAND\” when you interrupted me.”
echo “Quitting.”
exit 1
}
while :
do
echo -en “hello. “
sleep 1 (3 Replies)
Discussion started by: heman96
3 Replies
LEARN ABOUT OPENSOLARIS
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Process killing procedure configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap, scope.scope
DESCRIPTION
Unit configuration files for services, sockets, mount points, swap devices and scopes share a subset of configuration options which define
the killing procedure of processes belonging to the unit.
This man page lists the configuration options shared by these five unit types. See systemd.unit(5) for the common options shared by all
unit configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
information on the configuration file options specific to each unit type.
The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this unit shall be killed. One of control-group, process, mixed, none.
If set to control-group, all remaining processes in the control group of this unit will be killed on unit stop (for services: after the
stop command is executed, as configured with ExecStop=). If set to process, only the main process itself is killed. If set to mixed,
the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining
processes of the unit's control group. If set to none, no process is killed. In this case, only the stop command will be executed on
unit stop, but no process be killed otherwise. Processes remaining alive after stop are left in their control group and the control
group continues to exist after stop unless it is empty.
Processes will first be terminated via SIGTERM (unless the signal to send is changed via KillSignal=). Optionally, this is immediately
followed by a SIGHUP (if enabled with SendSIGHUP=). If then, after a delay (configured via the TimeoutStopSec= option), processes still
remain, the termination request is repeated with the SIGKILL signal (unless this is disabled via the SendSIGKILL= option). See kill(2)
for more information.
Defaults to control-group.
KillSignal=
Specifies which signal to use when killing a service. This controls the signal that is sent as first step of shutting down a unit (see
above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM.
Note that, right after sending the signal specified in this setting, systemd will always send SIGCONT, to ensure that even suspended
tasks can be terminated cleanly.
SendSIGHUP=
Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is
useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to "no".
SendSIGKILL=
Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the
service around. Takes a boolean value. Defaults to "yes".
SEE ALSO
systemd(1), systemctl(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7), kill(2), signal(7)
systemd 237 SYSTEMD.KILL(5)