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:
until (ssh root@10.1.1.39 2> /dev/null); do date; sleep 15; done
In this case will execute "date" then "sleep 15" until we are able to ssh into server, such as after a reboot
Could also be like:
until ( ping 10.1.1.39 1> /dev/null); do echo "server 10.1.1.39 is down"; sleep 15; done
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Not that it makes any significant difference in this case, but those parentheses around the commands are not necessary. Also, that ping command will go on pinging forever unless you give it a count with the -c option, and as far as I'm aware, GNU ping only sets an error code if it also fails to transmit any packets. Which means, as long as ping's able to transmit its echo requests, 'echo "server 10.1.1.39 is down"; sleep 15' won't run even if ping doesn't receive any responses.
yes the ping will need a -c arg - else it will as you say ping forever...