lsof -i -n -P | grep -e "$(ps aux | grep node | grep -v grep | awk -F' ' '{print $2}' | xargs | awk -F' ' '{str = $1; for(i = 2; i < NF; i++) {str = str "\\|" $i} print str}')"

dynamically list open files for a given process name

us lsof, grep for any pid matching a given name such as "node".
Sample Output
node      24903  rot   11u  IPv4 223478      0t0  TCP *:1337 (LISTEN)
node      24905  rot   11u  IPv4 223478      0t0  TCP *:1337 (LISTEN)
node      25256  rot   16u  IPv4 263849      0t0  TCP *:3000 (LISTEN)
node      25258  rot   11u  IPv4 263849      0t0  TCP *:3000 (LISTEN)
node      25259  rot   11u  IPv4 263849      0t0  TCP *:3000 (LISTEN)
node      25261  rot   11u  IPv4 263849      0t0  TCP *:3000 (LISTEN)
node      25262  rot   11u  IPv4 263849      0t0  TCP *:3000 (LISTEN)
node      25264  rot   11u  IPv4 263849      0t0  TCP *:3000 (LISTEN)

0
2015-02-14 23:24:00

These Might Interest You

  • If your customer deletes a file that is still in use by a process, that space does not get freed up (will not show up in df) until that process either closes the file on its own, or is killed.


    2
    lsof | egrep "^COMMAND|deleted"
    jyoder · 2009-03-12 23:11:26 0
  • Executing pfiles will return a list of all descriptors utilized by the process We are interested in the S_IFREG entries since they are pointing usually to files In the line, there is the inode number of the file which we use in order to find the filename. The only bad thing is that in order not to search from / you have to suspect where could possibly be the file. Improvements more than welcome. lsof was not available in my case Show Sample Output


    0
    for i in `pfiles pid|grep S_IFREG|awk '{print $5}'|awk -F":" '{print $2}'`; do find / -inum $i |xargs ls -lah; done
    giorger · 2013-01-24 13:57:19 0
  • A potential source of a full filesystem are large files left open but have been deleted. On Linux, a file may be deleted (removed/unlinked) while a process has it open. When this happens, the file is essentially invisible to other processes, but it still takes on physical space on the drive. Tools like du will not see it.


    0
    sudo lsof -nP | awk '/deleted/ { sum+=$8 } END { print sum }'
    jeffskinnerbox · 2015-09-19 00:45:23 3
  • I have come across a situation in the past where someone has unlinked a file by running an 'rm' command against it while it was still being written to by a running process. The problem manifested itself when a 'df' command showed a filesystem at 100%, but this did not match the total value of a 'du -sk *'. When this happens, the process continues to write to the file but you can no longer see the file on the filesystem. Stopping and starting the process will, more often than not, get rid of the unlinked file, however this is not always possible on a live server. When you are in this situation you can use the 'lsof' command above to get the PID of the process that owns the file (in the sample output this is 23521). Run the following command to see a sym-link to the file (marked as deleted): cd /proc/23521/fd && ls -l Truncate the sym-link to regain your disk space: > /proc/23521/fd/3 I should point out that this is pretty brutal and *could* potentially destabilise your system depending on what process the file belongs to that you are truncating. Show Sample Output


    16
    lsof +L1
    dopeman · 2010-07-14 17:21:01 2
  • Allows to check if shared library could be dynamically loaded


    0
    ldconfig -p | grep <somenewlib.so>
    al3x · 2009-02-07 23:15:38 0
  • List the files a process is using.


    16
    lsof +p xxxx
    rockon · 2009-03-02 04:49:23 0

What Others Think

OK, this command is much too long :-) . First, "ps | grep | grep -v grep"... you'd be better using pgrep or pidof pgrep node . Next you use xargs and awk to join up the numbers into one line. paste will do that for you with a choice of separators ... | paste -s -d\| -s means "serial" (on one line) -d delimiter of | (escaped with a backslash) . Then, change grep to -E to use extended regex syntax (this means we can search for (1234|4567) without backslashes. . The final command looks like: lsof -i -n -P | grep -E "($(pgrep node | paste -s -d\|))"
flatcap · 170 weeks and 4 days ago
btw, security by obscurity only works if you don't broadcast that your root user is called 'rot' ;-)
flatcap · 170 weeks and 4 days ago
Save the call to grep and just use lsof's -p option: lsof -p "$(pgrep node | paste -s -d\,)"
my_username · 169 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: