WEBVTT 00:01.070 --> 00:10.720 As you can see here, a new column titled The state here state team has been added to the output. 00:10.730 --> 00:19.010 So state is just a short for state and reveals the current status of the process. 00:19.010 --> 00:20.540 So let's actually. 00:21.750 --> 00:25.410 See what these are and understand more. 00:25.650 --> 00:29.000 So here, let's actually open our here. 00:29.040 --> 00:37.950 Uh, it seems that yes, actually here, this was from our previous lecture from permission and here. 00:37.950 --> 00:40.290 So now the are here. 00:40.290 --> 00:47.240 And as you can see here, we also have we have are the uppercase and lowercase else lowercase s and 00:47.250 --> 00:48.450 lowercase l. 00:49.480 --> 00:52.150 We also have this left row. 00:52.420 --> 00:55.350 And now you will understand all of these states here. 00:55.360 --> 01:00.430 So R means R means running. 01:00.430 --> 01:09.810 So this means the process is running or ready to run, and the uppercase s means sleeping. 01:09.820 --> 01:13.060 So the sleeping means the process is not running. 01:13.060 --> 01:24.310 Rather, it's waiting for an event such as a keystroke or a network packet, and D is in interruptible. 01:27.830 --> 01:30.710 Sleep in interruptible sleep. 01:30.710 --> 01:32.210 So the process is wait. 01:32.240 --> 01:36.100 Waiting for input outputs such as a disk drive. 01:36.110 --> 01:38.660 And we also have t. 01:38.690 --> 01:42.230 This t means stop. 01:42.380 --> 01:42.950 Stop. 01:42.950 --> 01:46.910 So this means that the process has been instructed to stop. 01:46.910 --> 01:50.540 So you will learn more about this in later lectures. 01:50.540 --> 01:53.540 And we also have uppercase s here. 01:53.540 --> 01:56.810 So this is zombie process. 01:56.930 --> 01:57.440 All right? 01:57.530 --> 01:58.220 Process. 01:58.220 --> 02:07.070 So this zombie process is a child process that has terminated but has not been cleaned up by its parent. 02:07.070 --> 02:08.900 So this is zombie process. 02:08.900 --> 02:14.960 And we also have this we also have this right row here. 02:14.960 --> 02:18.500 So this is a high priority. 02:20.030 --> 02:20.860 Process. 02:20.870 --> 02:25.080 So now I will explain what this high priority priority. 02:25.880 --> 02:26.510 Process is. 02:26.510 --> 02:30.920 So it's possible to grant more important importance to a process. 02:30.920 --> 02:33.390 So giving it more time on the CPU. 02:33.440 --> 02:37.640 So this property of a process is called niceness. 02:37.640 --> 02:45.320 So a process with a high priority is said to be less nice because it's taking more of the CPU time. 02:45.320 --> 02:48.620 So which leaves less for everybody else. 02:48.620 --> 02:53.690 And we also have here the uppercase N here. 02:53.690 --> 02:56.210 So this is a low priority. 02:56.210 --> 02:59.870 So a low priority process. 03:00.560 --> 03:07.430 So this is a process with a low priority and this is a nice process, Will and this will get this low 03:07.430 --> 03:09.010 priority process. 03:09.020 --> 03:17.090 We will get the processor to time only after the process with higher priority have been served. 03:17.090 --> 03:19.880 So it will comes after this. 03:21.950 --> 03:25.760 So this process state may be followed by other characters. 03:25.760 --> 03:29.900 So these states indicate various exotic process characteristics. 03:29.900 --> 03:32.510 So the C, the P is here. 03:32.510 --> 03:34.640 Actually, let me write that down here. 03:34.640 --> 03:38.390 So the P is also not clear. 03:38.390 --> 03:40.220 So the P is. 03:40.940 --> 03:43.010 Man page for more details. 03:43.010 --> 03:44.240 You can also watch here. 03:44.240 --> 03:48.500 So another popular set of options is Alex here. 03:48.620 --> 03:49.520 So p. 03:49.520 --> 03:58.880 S a u x, so and as in previous code, this is without dash. 03:58.880 --> 04:04.910 So and here and as you can see here, this gives us even more information. 04:04.910 --> 04:11.390 So this set of options displays the process belonging to every user. 04:11.390 --> 04:17.480 So using this option without deleting Dash invokes the command with BSD style behavior. 04:17.480 --> 04:24.710 So the Linux version of PS can emulate the behavior of the PS program found in several different Unix 04:24.710 --> 04:25.460 implementations. 04:25.460 --> 04:27.020 So with these options. 04:27.820 --> 04:29.860 We get additional columns here. 04:29.860 --> 04:38.740 As you can see, user ID, CPU, memory, CPU start, state start start time and command. 04:38.770 --> 04:41.320 Now I will explain all of this here. 04:41.320 --> 04:43.210 So the first year user. 04:43.510 --> 04:46.030 This is a user ID and this. 04:46.450 --> 04:50.350 And as you can see here, this means the owner of the process. 04:50.350 --> 04:54.160 So as you can see in this process is owner is root. 04:54.160 --> 05:00.280 And here when we come down here, as you can see here, owner is telephone, which is mousepad here 05:00.430 --> 05:05.320 that we opened right here and we also pass command itself. 05:05.590 --> 05:09.820 And this is lastly opened process here and here. 05:09.820 --> 05:13.230 As you can see here, we also have message plus polkit. 05:13.240 --> 05:16.420 This is different users for drivers and etcetera. 05:16.870 --> 05:17.680 So. 05:18.640 --> 05:19.630 Let's now go. 05:19.660 --> 05:28.090 Let's go to our what the process ID So obviously the process ID is just a process ID this gives it and 05:28.100 --> 05:31.000 the scanning a scanning order here. 05:31.090 --> 05:37.360 The last process gives a most process ID here and actually it's here. 05:37.360 --> 05:43.960 And this is the first process that we started in Spin in a splash when system started right here. 05:43.960 --> 05:47.740 So we also have the CPU. 05:47.980 --> 05:52.480 So this is the CPU usage in a percent here. 05:52.480 --> 05:55.000 As you can see, this takes multiple takes. 05:55.270 --> 05:58.660 Uh, almost 1% of my CPU here. 05:58.660 --> 06:02.710 We also have the memory usage present here. 06:02.710 --> 06:05.740 So this is the memory usage, just the memory usage present. 06:05.740 --> 06:07.870 As you can see, most of this takes zero. 06:07.870 --> 06:13.390 And here our terminal takes to almost 3% of our. 06:15.390 --> 06:16.470 A memory usage. 06:16.470 --> 06:25.440 And as you can see from it, that we use for drawing things on the screen actually takes the 2% of my 06:25.440 --> 06:28.290 memory on my computer here. 06:28.290 --> 06:31.950 So let's go to our. 06:32.960 --> 06:34.070 RSS. 06:34.100 --> 06:37.160 This is actually a resident set size. 06:37.160 --> 06:41.540 So this is the amount of physical memory, the RAM, random access memory. 06:41.990 --> 06:44.960 The process is using in kilobytes here. 06:44.960 --> 06:51.530 And as you can see, RSS, it's actually takes, uh, 12180. 06:52.670 --> 06:53.510 Kilobytes. 06:53.510 --> 06:56.120 And we also have VCs here. 06:56.120 --> 06:58.400 So this is the virtual memory size. 06:59.480 --> 07:01.580 And here we also have START. 07:01.580 --> 07:04.820 So this is a time, the time when the process started. 07:04.820 --> 07:13.820 So for a value and these are actually values over, uh, 24 hours here, as you can see here, this 07:13.820 --> 07:14.810 is 24. 07:14.900 --> 07:16.220 24 hours. 07:16.220 --> 07:21.800 So that's it with our comment in next lecture, you will also learn the top comment. 07:21.800 --> 07:23.600 So I'm waiting you in the next lecture.