06-05-2016
There appears to be one or a group of processes - maybe a service - that run and then stop periodically. What process(es) writes to the sdh drive?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi guys,
i am having a dual cpu xeon machine.
i came to know that i can view the performance by giving top command.
but top command shows only the usage of one cpu in percentage
while the process are using more than 100% usage in the list .
can i know separately the usage of cpus.
can you... (5 Replies)
Discussion started by: bijuhpd
5 Replies
2. SCO
Is there a command in SCO Unix that does the same as the top command in HPUX. The command displays the jobs using the most system resources.
Thanks You (0 Replies)
Discussion started by: joestrosser
0 Replies
3. AIX
Is there a 'top' command equivalent in AIX 4.2 ?
I already checked and I do not see the following ones anywhere:
top
nmon
topas (1 Reply)
Discussion started by: Browser_ice
1 Replies
4. Shell Programming and Scripting
Hi all,
I found like top command could be used to find the Memory and CPU utilization. But i want to know how to find the Memory and CPU utilization for a particular user using top command.
Thanks in advance.
Thanks,
Ananthi.U (2 Replies)
Discussion started by: ananthi_ku
2 Replies
5. Solaris
Iostat inquiry;# iostat -e
---- errors ---
device s/w h/w trn tot
fd0 0 0 0 0
md0 0 0 0 0
md1 0 0 0 0
md2 0 0 0 0
md10 0 0 0 0
md11 0 0 0 0
md12 0 0 0 0
md30 0 0 0 0
md31 0 0 0 0
md32 0 0 0 0
md40 0 0 0 0
md41 0 0 0 0
md42 0 0 0 0
md50 0 0 0 0
md51 0 0 0 0
md52 0 0 0 0
md60 0 0 0... (2 Replies)
Discussion started by: pepi
2 Replies
6. Solaris
Hello everyone,
Can you please explain me what kind of information do IOSTAT show ?
iostat -xnz 3 show me those informations:
The I/O of the c0t0d0 disk is normal ?
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 ... (3 Replies)
Discussion started by: adilyos
3 Replies
7. Solaris
Hi Everyone,
I try to calculate the total hard disk space of a solaris machine using iostat -En command. Iterating the output and summing up all the number present near the Size: will give the exact size of the harddisk. But it is not working for a machine.
This command works in many flavors... (2 Replies)
Discussion started by: prasankn
2 Replies
8. SuSE
Hi,
my os is SLES 10
from sort
iostat
as my output does not include rkB/s and wkB/s I probably have to adjust the key position, so
is the following iostat pipe to sort service request command correct?
oracle@vmc_stallite:~> iostat -x | sort -nrk11
sda 0.96 ... (4 Replies)
Discussion started by: jediwannabe
4 Replies
9. Shell Programming and Scripting
Hi,
I have a requirement where parsed output from various linux commands like top, netstat, iostat, etc. will be the input for one javascript with the parsed output from these commands converted to JSON format
For "iostat" command, since there are two outputs - one w.r.t CPU utilization and... (2 Replies)
Discussion started by: gopivallabha
2 Replies
10. Shell Programming and Scripting
Hi,
I got the code below is one of the threads from this forum.
lineCount=$(iostat | wc -l)
numDevices=$(expr $lineCount - 7);
iostat $interval -x -t |
awk -v awkCpuFile=$cpuFile -v awkDeviceFile=$deviceFile -v awkNumDevices=$numDevices '
BEGIN {
print... (2 Replies)
Discussion started by: gopivallabha
2 Replies
LEARN ABOUT OPENDARWIN
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)