Skip to main content

lsof command and options

lsof - list open files. An  open file may be a regular file, a directory, a block special file, a character special file, an executing text reference, a library, a stream or a network file (Internet socket, NFS file or UNIX domain socket.)  A specific file or all the files in a file system may be selected by path. Given that this command identifies which files are being used, this information can be used when disk can not be unmounted due to files being used or opened.
Type the following command:
$lsof
    lsof.png
Herein -
FD – stands for File descriptor and may have some of the values as:
  1. cwd current working directory
  2. rtd root directory
  3. txt program text (code and data)
  4. mem memory-mapped file
Also in FD column numbers like 41u is actual file descriptor and followed by u,r,w of it’s mode as:
  1. r for read access.
  2. w for write access.
  3. u for read and write access.
TYPE – of files and it’s identification.
  1. DIR – Directory
  2. REG – Regular file
  3. CHR – Character special file.
  4. FIFO – First In First Out
  5. IPv4
  6. IPv6
OPTIONS
-u s selects the listing of files for the user whose login names or user ID numbers are in the comma-separated set s -  e.g.,  ``abe'', or ``548,root''.  (There should be no spaces in the set.)
    $lsof -u tarun
-i [i] selects the listing of files any of whose Internet address matches the address specified in i. If no address is specified, this option selects the listing of all Internet and x.25 (HP-UX) network files. Following command lists all network connections listening and established -
$lsof -i
Screenshot from 2015-07-22 14:35:31.png
An Internet address is specified in the form (Items in square brackets are optional.):
[46][protocol][@hostname|hostaddr][:service|port]
    $lsof -i TCP:80
Screenshot from 2015-07-22 14:13:46.png
List running processes of open files of TCP port range from 1-800
    $lsof -i TCP:1-800
Screenshot from 2015-07-22 14:25:27.png
If -i4 or -i6 is specified with no following address, only files of the indicated IP version, IPv4 or IPv6,  are  displayed.
    $lsof -i4
    Screenshot from 2015-07-22 14:22:02.png
    $lsof -i6
Screenshot from 2015-07-22 14:22:30.png

-p s excludes or selects the listing of files for the processes  whose  optional  process  IDentification  (PID)  numbers  are  in  the comma-separated set s - e.g., ``123'' or ``123,^456''.  (There should be no spaces in the set.) PID numbers that begin with `^' (negation) represent exclusions.

        $lsof -p 2499

-t   specifies  that  lsof  should  produce  terse output with process identifiers only and no header - e.g., so that the output may be piped to kill(1)

        $lsof -p 2499

        $kill -9 `lspf -t -u tarun`

Popular posts from this blog

Distributed Load Testing with JMeter

Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred

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

XPath and single quotes

I had tough time dealing with XPath and single quote. Though W3C recommends using ' to escape it but I never got it working, let me know if any of you get through. Came across this blog and found that “concat” could be used in this situation. So original XPath expression is – //meta[@name=’DESCRIPTION’][@content=’Tester’s Test’] This is some thing which certainly fails as single quote in “Tester’s” marks it at end of string and then XPath blows up, next trial was – //meta[@name=’DESCRIPTION’][@content=’Tester''s Test’] This does not work despite w3c recommendation! And then I used concat function and split the string as – concat(‘Tester’,”’”,’s Test’) NOTICE that single quote is kept in double quote while other characters are kept in single quotes. So XPath looks as – //meta[@name=’DESCRIPTION’][@content=concat(‘Tester’,”’”,’s Test’)] And this works charm.