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/
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.
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
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:
Shows updated status in a terminal window for connections to port '80' in a human-friendly form. Use 'watch -n1' to update every second, and 'watch -d' to highlight changes between updates.
If you wish for status updates on a port other than '80', always remember to put a space afterwards so that ":80" will not match ":8080".
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
nice but won't tell me which vhost the connection went to or to which hosted site. any chance to see this info too?
watch -dn2 'netstat -anptu | egrep "^Proto|:80" | sort'will watch on ports 80 and 8080 and sort output if u have a lot of connections, highliting changes with update interval 2 sec.
Ovidiu: When you say vhost, do you mean a protocol thing, like the domain part of the "RCPT TO:" lines of SMTP? In that case, you'll need packet inspection -- you're better off doing a 'tail -f logfile |grep ' instead.
ilrandir : I already mentioned using other values for "-n" in the comment.