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:
Bash scrip to test if a server is up, you can use this before wget'ing a file to make sure a blank one isn't downloaded.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
If you're not going to have an "else" clause, you can shorten that to:
[ "$(ping -q -c1 google.com)" ] && wget ...'if' works by using the '[' (test) command, but you can use it directly.
Alternatively (not as pretty):
ping -c1 google.com > /dev/null && wget ...Wouldn't it be better to use curl -I to check the headers for a 200 OK? Just because a machine is responding to pings, that doesn't mean that the webserver is up.
I don't have the means to test this example at the moment, but I believe it should work.
curl -Is google.com 2>&1 | grep -q "200 OK" && wget ...Great alternatives, I'll have to give these a try!
'if' expects a command. '[' is actually a program, not part of the shell. So you can actually just do
if ping -q -c1 google.com; then ...No need for the 'then' or even an 'else', just use && or ||
e.g.:
ping -c1 host.com > /dev/null && echo "YES" || echo "NO"This is the equivalent of:
if ping -c1 host .com > /dev/nullthenecho "YES"elseecho "NO"fi