02-18-2013
As I recall, vmstat needs some help to see all your disks and such. The default set may be a subset.
Zombies are more specifically caused when the parent is not honoring SIGCHLD, so the notification at the bitter end of child life cannot be passed. The rcp/rsh family was famous for this. I guess paranoid programmers block signals rather than accept one of the default handlers. Interactive shells can have a sort of zombie when background processes stop for terminal i/o or termination notification. Check out the PPID, any shared tty processes of the zombies to see if there is a pattern to them. They take up a process slot but do not have a lot of overhead, so do not get OCD about them when you have bigger fish to fry to fix your slow system.
I have seen systems crawl for desperate lack of swap space, but with all those zeros, swap seems out fo the picture. Check, though!
Is this Oracle slowness or shell ?
Last edited by DGPickett; 02-20-2013 at 01:40 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
How do you reset the values that vmstat displays?
Vmstat displays a running average from the last the system was restarted on the first line, how do you reset these values without restarting the system? (Solaris 8) (3 Replies)
Discussion started by: kuczerp
3 Replies
2. UNIX for Dummies Questions & Answers
When I exeute vmstat (e.g. vmstat 30 2),
in some machines I get some wierd result as the first line.
like: -117% or 208% for CPU idle percentage.
But the second line is alright.
Could someone explain this please.
Thanks !
Chaadana (4 Replies)
Discussion started by: chaandana
4 Replies
3. UNIX for Dummies Questions & Answers
Hi
I wanted to collect data by using vmstat -I 60 >xxxx.txt & using my own account
It was stopped by it self after 2 hours try again same result
We want to collect day date by succession how to collect data using vmstat for day
Thank you (2 Replies)
Discussion started by: Syed_45
2 Replies
4. Linux
Hi everyone,
I need to see some VM manager performance/behavior information on some Linux boxes regarding pages scanned/activation of the paging algorithm in order to get an idea if a given server needs more memory and is actually paging. In Aix servers, by using the vmstat cmd you... (1 Reply)
Discussion started by: jcpetela
1 Replies
5. Shell Programming and Scripting
I have a list of Servers in no particular order as follows:
virtualMachines="IIBSBS IIBVICDMS01 IIBVICMA01"And I am generating some output from a pre-existing script that gives me the following (this is a sample output selection).
9/17/2010 8:00:05 PM: Normal backup using VDRBACKUPS... (2 Replies)
Discussion started by: jelloir
2 Replies
6. AIX
Hi AIX Expert,
the fr (page freed/page replacement) and sr (pages scanned by page-replacement algorithm) values from the vmstat output (see below please) are very high. I usually see this high value during the oracle database backup. In addition, the page scan/page steal/ page faults values... (7 Replies)
Discussion started by: Beginer0705
7 Replies
7. Shell Programming and Scripting
I have searched in a variety of ways in a variety of places but have come up empty.
I would like to prepend a portion of a section header to each following line until the next section header. I have been using sed for most things up until now but I'd go for a solution in just about anything--... (7 Replies)
Discussion started by: pagrus
7 Replies
8. Programming
I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this :
i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies
9. Linux
I m checking idle time using vmstat, below are the results
var=$(ssh wmtmgr@$hostname vmstat | tail -1 | awk '{print $15}')
89
and now im subtracting 89 with 100 & im getting expected results
expr 100 - $var
11
Now How can I get the result 11 in one line code? (4 Replies)
Discussion started by: sam@sam
4 Replies
10. Programming
Oddities with gcc, 2.95.3 for the AMIGA and 4.2.1 for MY current OSX 10.14.1...
I am creating a basic calculator for the AMIGA ADE *NIX emulator in C as it does not have one.
Below are two very condensed snippets of which I have added the results inside the each code section.
IMPORTANT!... (11 Replies)
Discussion started by: wisecracker
11 Replies
LEARN ABOUT CENTOS
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Kill environment configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap
DESCRIPTION
Unit configuration files for services, sockets, mount points and swap devices share a subset of configuration options which define the
process killing parameters of spawned processes.
This man page lists the configuration options shared by these four unit types. See systemd.unit(5) for the common options of all unit
configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5) and systemd.mount(5) for more information on the specific
unit configuration files. The execution specific configuration options are configured in the [Service], [Socket], [Mount], or [Swap]
section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this service shall be killed. One of control-group, process, none.
If set to control-group, all remaining processes in the control group of this unit will be terminated 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 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.
Defaults to control-group.
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.
KillSignal=
Specifies which signal to use when killing a service. Defaults to SIGTERM.
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(8), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7)
systemd 208 SYSTEMD.KILL(5)