dynamically list open files for a given process name

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}')"
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)

2015-02-14 23:24:00

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 · 308 weeks and 6 days ago
btw, security by obscurity only works if you don't broadcast that your root user is called 'rot' ;-)
flatcap · 308 weeks and 6 days ago
Save the call to grep and just use lsof's -p option: lsof -p "$(pgrep node | paste -s -d\,)"
my_username · 308 weeks and 1 day 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: