Skip to main content

top command and options

Back to performance measurement commands

The top program provides a dynamic real-time view of a running system.  It can display system summary information as well as a list of processes or threads currently being managed by the Linux kernel.

Type the following command:

$ top
top.png

The top command used to display all the running and active real-time processes in ordered list and updates it regularly. Press ‘c‘ option in running top command, it will display absolute path of running process.
If you want to kill a running process then use kill command as - {kill -9 <process-id>}

Press (Shift+W) to save the running top command results under /root/.toprc.

OPTIONS

-u | -U  :User-filter-mode as:  -u | -U number or name
Display only processes with a user id or user name matching that given.  The '-u' option matches on  effective user whereas  the  '-U' option matches on any user (real, effective, saved, or filesystem).

Prepending  an  exclamation point ('!') to the user id or name instructs top to display only processes with users not matching the one provided.

$ top -u tarun

replace tarun with your username ;-)

top.png


-c  :Command-line/Program-name toggle Starts top with the last remembered 'c' state reversed. Thus, if top was displaying command lines, now that field will show program        names, and visa versa. See the 'c' interactive command for additional information. You can use this command to display absolute path of running process.


        $ top -u tarun

        top.png

-d  :Delay-time interval as: -d ss.t (secs.tenths) Specifies the delay between screen updates, and overrides the corresponding value in one's personal configuration file or the startup default.

        $ top -d 1

        No screen capture, try it yourself ;-)

Popular posts from this blog

Using xPath to reach parent of an element

Note: If you are new to java and selenium then start with selenium java training videos .   I prefer css locator over xPath but there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also hig...

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Should selenium tests be always independent? The endless debate !!

Though unit tests have always recommended to be independent of each other, advent of selenium+TestNG has given birth to dependent integration/end to end tests. TestNG Author Cédric Beust had written about it few years ago. When I had begun writing selenium tests I used to launch browser once in one test class and test methods were usually dependent on one another. Hence 2nd test method would begin test run on same browser + application state where 1st test method stopped. Launching just one browser for five or more test methods in a class is big time saving is not it? Well not really, for the reasons I am going to describe in this post. Since then I have moved on to launching browser per test method but yet give in “charm” of dependent test methods at times. to So here are the few pros and cons for dependent tests and - Pros - Similar steps of execution don’t have to be repeated in multiple tests when steps constitutes a test method in themselves If login fails then...