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.

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

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Wait the end of prog1 and launch prog2

Terminal - Wait the end of prog1 and launch prog2
pkill -0 prog1; while [ $? -eq 0 ]; do sleep 10; pkill -0 prog1; done; prog2
2011-02-11 21:46:42
User: Saorel
Functions: sleep
2
Up
Down
Wait the end of prog1 and launch prog2
Add to favourites | Report as malicious

Alternatives

There are 7 alternatives - vote for the best!

Terminal - Alternatives
while pkill -0 prog1; do sleep 10; done; prog2
2011-02-12 02:53:53
User: daa
Functions: sleep
1
Up
Down
Wait the end of prog1 and launch prog2
Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

OMG, what's that? What's wrong with

prog1;prog2

or

prog1 && prog2

Comment by zolden 118 weeks and 4 days ago

@zolden,

Suppose prog1 is already running and you need prog2 to start after prog1 exits. However, there is a simpler way to do what the submitter has proposed:

while pkill -0 prog1; do sleep 10; done; prog2
Comment by daa 118 weeks and 3 days ago

@daa, yes you're right. But i 've just found another simpler :

press Ctrl+Z to suspend prog1 then :

fg && prog2
Comment by Saorel 118 weeks and 2 days ago

Nevertheless if you don't have hand on prog1, it's a good means to wait.

Comment by Saorel 118 weeks and 2 days ago

@daa you should submit this :)

Comment by FRUiT 118 weeks and 2 days ago

@FRUiT, I submitted it two days ago but and I'm still waiting the command to pass through the moderation.

Comment by daa 118 weeks and 2 days ago

Thank you ^^

Comment by FRUiT 118 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts