Most of services are under SMF control so you can use
to enable service
to disable service
to restart service
for killig process , you use signals we have too mnay signals , but most importanat are -9 to kill (last solution) and 15 (kill signal but enable to process to clean his own trash)
so
to find out parent - child process you can use
every child process has hit own unique PID and you can kill them
using or pkill or kill command
I'm a newbie to the Unix world Help!
I have to maintain a host of Sybase database servers sitting on Unix Sun Solaris 8...I've been tasked with finding/creating a way to auto start/stop Unix via unix commands, specifically when the Unix servers need to be restarted we want Sybase to start... (2 Replies)
Hi everyone, I was wondering how to configure ftp access for one user when I found this board.
After some searches I found my infos around proftpd (and the great config file proftpd.conf who answered to all my dreams...)
but now I only need to stop proftpd and restart it (I guess it is needed... (1 Reply)
Hi,
I have 2 start and stop sh.
Start sh
--------
This will start few processes.
Example code:
echo "start process : lgz200 /pipe=test_jobs"
nohup lgz200 /db=test/test1@test1 /pipe=test_jobs > ../log/lgz200_j.log &
echo "echo \"stop process (pid=$!): lgz200 /pipe=test_jobs\"" >>... (3 Replies)
I am in the process of reorging my Lawson db. I need to turn off the RMI server...not a problem. However my instructions also state that I must also
shutdown my Servlet Container....I believe it is Apache.
I have looked in /usr/apache/bin/apachectl
What is the command for stopping and... (2 Replies)
Hi all,
I joined this forum today and this is my first question. I thank you all for viewing it. I will try to be brief.
The OS: HP-UX B.11.11 U 9000/800
There are lot of cron scheduled perl scripts running on this server, which do different things at different time. Some of them process... (10 Replies)
I'm wondering how I should make a script that can start, stop, and restart another script.
What I need to be able to do, is start and stop a perl script from the command line. The easiest way of doing this seems to be to have another script, starting and stopping the other script. I have BASH,... (7 Replies)
HI
I am using below code to start and stop servers but it is not working ,how to run the script please suggest me ,if any errors in the script please let me know.
#!/bin/bash
IMS_START="/Webserver/AppServer/bin/startServer.sh"
IMS_STOP="/Webserver/AppServer/bin/stopServer.sh"
case "$1" in
... (1 Reply)
Is there any functional difference between:
issuing separate stop/start commands like this;
super (handler) (instance) stop
super (handler) (instance) start
versus issuing a single recycle command like this;
super (handler) (instance) restart (3 Replies)
Hi there,
I've install a testserver with SLES 11.0! I'll install/test XEN + WebServer not all things at the moment!
In a first time, I'd like to stop all unuse processes... but I don't understand all processes!
As someone a list of all processes with his signification and which should/could... (3 Replies)
Another question for you guys! This is so fun.
So I am playing around with the factor operation. I read in "man factor" that you can actually print a list of primes in between a range, using the syntax
factor ]
However, every time I enter two values, it just returns the factored value.... (1 Reply)
Discussion started by: statichazard
1 Replies
LEARN ABOUT SUNOS
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 237SYSTEMD.KILL(5)