Show the command line of a process that use a specific port (ubuntu)

port=8888;pid=$(lsof -Pan -i tcp -i udp | grep ":$port"|tr -s " " | cut -d" " -f2); ps -Afe|grep "$pid"|grep --invert-match grep | sed "s/^\([^ ]*[ ]*\)\{7\}\(.*\)$/\2/g"
A way not so simple but functional for print the command for the process that's listening a specific port. I got the pid from lsof because I think it's more portable but can be used netstat netstat -tlnp
Sample Output
java -Xmx1024m -XX:MaxPermSize=300m -server -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8885 -jar /oc4j/j2ee/home/oc4j.jar 

2010-01-11 17:49:22

1 Alternatives + Submit Alt

What Others Think

Why not just simply: lsof -i:8888
din7 · 620 weeks and 5 days ago
because lsof -i:8888 do not show the command executed, in my sample the show is only: lsof -i:8888 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME java 1949 username 213u IPv6 12317041 TCP *:8888 (LISTEN) my way show the full command line: port=8888;pid=$(lsof -Pan -i tcp -i udp | grep ":$port"|tr -s " " | cut -d" " -f2); ps -Afe|grep "$pid"|grep --invert-match grep | sed "s/^\([^ ]*[ ]*\)\{7\}\(.*\)$/\2/g" java -Xmx1024m -XX:MaxPermSize=300m -server -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8885 -jar /oc4j/j2ee/home/oc4j.jar -err I think usefull... if you know other way, let me now.
glaudiston · 620 weeks and 5 days ago
lsof gets you the pid, and you can get the command line from /proc/$pid/cmdline, at least in linux.
bwoodacre · 620 weeks and 5 days ago
thanks to bwoodacre: cat /proc/$(lsof -ti:8888)/cmdline
glaudiston · 614 weeks and 3 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? 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.


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: