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:
Let me suggest using wget for obtaining the HTTP header only as the last resort because it generates considerable textual overhead. The first ellipsis of the sample output stands for
Spider mode enabled. Check if remote file exists.
--2009-03-31 20:42:46-- http://www.example.com/
Resolving www.example.com... 208.77.188.166
Connecting to www.example.com|208.77.188.166|:80... connected.
HTTP request sent, awaiting response...
and the second one looks for
Length: 438 [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
slightly easier with curl tho:
curl -I http://www.example.comrealgt, that issues a HEAD request though, which may not be supported by the server whereas what I really want is the GET request, but display only the headers.
curl --head http://www.example.com
curl is easer. in general curl is always simpler to use then any other like wget, lynx, etc
Agreed curl is the best. I always do:
curl -sv http://www.example.com > /dev/null
to get just the client and server headers.
This is a perfect command CURL uses more memory and resources than wget and is less commond on routers and minilinux.