Hide

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.

OpenID
or
Sign in Register

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

World cup college
Hide

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:

Hide

News

2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
2009-05-17 - Added duplicate suggestions to the new command form
When adding a new command, a quick background search is performed to make sure you're not duplicating a command already in the system.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Lists all listening ports together with the PID of the associated process

Terminal - Lists all listening ports together with the PID of the associated process
netstat -tlnp
2009-02-15 14:20:25
User: fulat2k
Functions: netstat
83
Up
Down
Lists all listening ports together with the PID of the associated process

The PID will only be printed if you're holding a root equivalent ID.

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
netstat -nptl
2009-12-11 10:23:43
User: sputnick
Functions: netstat
4
Up
Down
List all TCP opened ports on localhost in LISTEN mode

Alternative of OJM snippet :

This one show the IP too, where ports bind. It's very important, because if there's only 127.0.0.1 instead of 0.0.0.0, connections from internet are rejected.

Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

BSD equivalent:

sockstat -l4

(that's a small L)

Comment by lme 50 weeks and 6 days ago

for german users there is a simple way to remember a similar command:

netstat -tulpen

(tulpen = tulips in german)

Comment by Hollow 48 weeks and 2 days ago

I prefer:

netstat -paten

also easy to remember :-) and gives not only listening ports, but also running processes and their owning users

p.s. mnemonic of course is

netstat -patent

but 2nd t is simply redundant

Comment by vleolml 43 weeks and 3 days ago

Following will also show UDP sockets:

netstat -tulnp
Comment by realist 29 weeks and 2 days ago

lsof -Pan -i tcp -i udp

Comment by solarislackware 14 weeks ago

not for OS-X :(

Comment by ab 2 weeks and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts