05-10-2005
Is INTR a flag or a command ?
In my case , is there any solution except killing manually the process ?
thanks
Christian
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
If I try to run "kill -14 pid", some processes in my application
get terminated , while some keeps running.
If SIGALRM signal is sent, they should make an exit.
What's the reason any process keeps on running. (1 Reply)
Discussion started by: poojac
1 Replies
2. UNIX for Dummies Questions & Answers
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
Discussion started by: Lokesha
4 Replies
3. UNIX for Advanced & Expert Users
Hi,
I mean Unix Linux general solution, so please don't move my question, as it's Unix specific.
I would like to remotely control my "full" Linux router.
Already succeeded to compile Linux Unix dialog, running some tests.
The issue is dialog comes with a limited number of widget boxes for... (4 Replies)
Discussion started by: jack2
4 Replies
4. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
5. Shell Programming and Scripting
Hello All,
I was looking into creating a script that would be used only to start a Daemon and create a lock file...
F.Y.I. It's for Nagios' NRPE Daemon Plugin...
Anyway when I run the command to start the Daemon (below):
/usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d
And... (14 Replies)
Discussion started by: mrm5102
14 Replies
6. Tips and Tutorials
For the newbies, I should have posted this years ago....
Here is the standard (tiny) "bread and butter" perl script (on Linux) I use in my crontab files to insure key processes are alive ( just in case ! ) like httpd, named, sshd, etc.
The example below if for named......
... (1 Reply)
Discussion started by: Neo
1 Replies
7. UNIX for Dummies Questions & Answers
How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address
and column 3 contains “cc” e-mail address to include with same email.
Sample input file, email.txt
Below is an sample code where... (2 Replies)
Discussion started by: asjaiswal
2 Replies
8. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
9. AIX
Hi 2 all,
i have had AIX 7.2
:/# /usr/IBMAHS/bin/apachectl -v
Server version: Apache/2.4.12 (Unix)
Server built: May 25 2015 04:58:27
:/#:/# /usr/IBMAHS/bin/apachectl -M
Loaded Modules:
core_module (static)
so_module (static)
http_module (static)
mpm_worker_module (static)
... (3 Replies)
Discussion started by: penchev
3 Replies
LEARN ABOUT ULTRIX
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)