What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.




Report the established connections for a particular port

Terminal - Report the established connections for a particular port
export PORT=11211; ss -an4 | grep -E "ESTAB.*$PORT" | awk '{print $5}' | awk -F: '{print $1}' | sort | uniq -c | sort -nr
2014-04-25 13:15:48
Functions: awk export grep sort uniq
Report the established connections for a particular port


There are 4 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Hmm... first I tried to do this entirely in awk, but that got a bit complicated.

Instead, I've gone for replacing your "grep;awk;awk" with one "sed":

export PORT=11211; ss -an4 | sed -n '/ESTAB.*:'$PORT' .*:/{s/.* \([^:]\+\):.*:.*/\1/p}' | sort | uniq -c | sort -nr

It consists of three parts. A search:

'/ESTAB.*:'$PORT' .*:/

A replace:

s/.* \([^:]\+\):.*:.*/\1/

and print

sed -n ... p
Comment by flatcap 48 weeks ago

this provides a very different report.

export PORT=11211; ss -an4 | grep -E "ESTAB.*$PORT" | awk '{print $5}' | awk -F: '{print $1}' | sort | uniq -c | sort -nr












export PORT=11211; ss -an4 | sed -n '/ESTAB.*:'$PORT' .*:/{s/.* \([^:]\+\):.*:.*/\1/p}' | sort | uniq -c | sort -nr


Comment by hornetmadness 48 weeks ago

This is interesting. I had not yet played with "ss". I thought I could cut out some of the pipes to make it all faster while still using ss, but I couldn't. I did find a slightly different approach.

PORT=22 ; ss -n4 -o state established "( dport = :$PORT or sport = :$PORT )" | awk -F ':| +' '$1 ~ /[0-9]+/ {print $5}' | sort | uniq -c | sort -nr

I also noticed that when I had PORT=22 the 'grep -E "ESTAB.*$PORT"' also matched port 8022. It should probably at least be changed to:

grep -E "ESTAB.*:$PORT "

I also tried with lsof, but that was much slower:

PORT=ssh ; lsof -itcp:$PORT -stcp:established -n |awk -F '>|:| +' '$2 ~ /[0-9]+/ {print $11}' | sort | uniq -c | sort -rn
Comment by pdxdoughnut 47 weeks and 4 days ago

Your point of view

You must be signed in to comment.