[O & M engineer _ 03] 20 built-in Linux monitoring tools: w and ps

[Personnel in O & M _ 03] 20 built-in monitoring tools for Linux systems: the third article of w and ps personnel's O & M on chinamoocs has been published, and I have to seek help from each other. If you are interested in the theme, please refer to it. article 1: [Personnel in O & M transit _ 01] 20 built-in monitoring tools for Linux systems: top 2: [Personnel in O & M transit _ 02] 20 built-in monitoring tools for Linux systems: what about the vmstat and netstat (4) w who commands? Do you remember wood? The old habit is to show you a piece of output: [plain] [root @ MPEG-4 ~] # W 16:57:10 up 2 days, 5 users, load average: 0.08, 0.03, 0.00 user tty from login @ idle jcpu pcpu what root pts/0: 1.0 Thu11 2 days 0.00 s 0.00 s bash root pts/1 129.38.54.166 33 0.00 s 0.01 s 0.00 s w root pts/2: 2.0 Thu11 2 days 0.00 s 0.00 s bash root pts/3 166.35.34.113 20.00 s 0.02 s 0.02 s top root pts/8: 3.0 3: 20 m 0.01 s 0.01 s bash obviously, w output can be divided into two parts as part 1st, very familiar .... ah, yo ~ The world is really small, and it hits the top bird ~~~ In order to take care of the aforementioned "best practices", for section 2, Rocky thinks that if you pay attention to WHAT, WHAT is a magic horse ~~~ WHAT: Who is the currently running command, and who is talking about you? 166.35.34.113. I am currently running top, maybe I am too short? Haha, and ⑸ ps are important. It's a great man, a great god, and a legend of life that makes us welcome ps birds in tears. What? Ps, isn't that the Goddess's strongest cosmetics? Let's take a look at it, and change the way it is, and let the best practices be stranded for the moment, Rocky thinks, ps is often used, simply come to "best use habits ": "ps-ef | grep oo" "ps aux | grep xx" weak Q: Is there a "-" in front of the aux? Yes, no! Ah, ah, bright and blind the aluminum alloy dog eye of laoxi. Rocky is going to talk about the best use habit of "ps aux". First, let's look at the output of ps aux [plain] [root @ Xilinx. ~] # Ps aux user pid % CPU % mem vsz rss tty stat start time command root 1 0.0 0.0 10348 692? Ss Mar28 init [5] root 2 0.0 0.0 0 0? S <Mar28 [migration/0] root 3 0.0 0.0 0 0? SN Mar28 [ksoftirqd/0] ***** N output rows are omitted here ********* oracle 32260 0.0 0.6 671488? Ss ora_j000_cdio2010 root 32275 0.0 0.0 65580 pts/3 R + ps aux for this output, I have talked about it earlier. Here we talk about table: ① STAT: the Current Status and main status of the process are: I R (Running): The process is Running, Ⅱ S (Sleep): The process is currently in Sleep status (idle), but can be awakened Ⅲ D (Defunct): The sleep state that cannot be awakened, usually this process may be waiting for I/O IV T (stop ): stop status, which may be in work control or debugging status v Z (zombie ): botnets, programs that have been terminated, but still occupy resources, but do not know "there is a kind of love to let go" ② START: the TIME when the process is triggered ③ TIME: actual CPU consumption time ④ COMMAND: What is the sacred COMMAND that triggers the process?