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

Where is my defect ID?

Don't you feel ecstatic when your automated tests find bug? After all tests finding bugs give us a sense of accomplishment, is not it? And this is followed by usual cycle of defect reporting, retesting and hopefully closure of defect. But at times defects are deferred to next or future releases. Which causes test method to fail for subsequent releases. And if you are dealing with a test suite having 100s of tests then it may become difficult to remember if there was a defect reported for a failing test? How do you deal with such situation. How about adding defect-id to @description tag of TestNG test. Hence it is reported on automated test report and we would know if defect exists for a failing test - How do you track defect-id of a failing test?

Return only first or last element from webelements collection

We often come across situation when there are multiple elements on a page and we probably like to exercise only a few of them using selenium webdriver. May be just first and last element. For example on a search result page we may like to click on only first and last link and not all. This is when Iterables API comes handy. (By the way I am assuming that you have already completed watching selenium training videos :)). Once we have collection of web element then we can use Iterables to get only first or last element as following - Consider that we fetch collection of element as - List< WebElement > webElements = getDriver().findElements(By. id ( "htmlID" ));   Now we can get the first web element from this collection as -  WebElement firstElement = Iterables. getFirst (webElements,  getDriver().findElement(By. id ( "defaultElement" )));   Herein second argument -   (getDriver().findElement(By. id ( "defaultElement" )))    in the me

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro