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.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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:



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.

Top Tags





Manually Pause/Unpause Firefox Process with POSIX-Signals

Terminal - Manually Pause/Unpause Firefox Process with POSIX-Signals
killall -STOP -m firefox
2009-05-18 20:02:44
Functions: killall
Manually Pause/Unpause Firefox Process with POSIX-Signals

Continue with:

killall -CONT -m firefox

Suspends all Firefox Threads. Results in Zero CPU load.

Useful when having 100+ Tabs open and you temporarily need the power elsewhere.

Be careful - might produce RACE CONDITIONS or LOCKUPS in other processes or FF itself.

matching is case sensitive.


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think


Alternatively, exit Firefox and reduce the number of tabs rather than pausing then continuing to use more. :-)

Comment by mpb 310 weeks and 3 days ago

My Firefox suffers from incurable chronic tabitis. :(

But I hear task-based navigation is just around the corner :)

Comment by Schneckentreiber 308 weeks and 3 days ago

My recent Jaunty is not allowing -m option.

However following worked, nice command

killall -STOP firefox

killall -CONT firefox

Comment by tejparkash 306 weeks and 4 days ago

This is great. Do you know how to do this in Windows?

Comment by mawriz 281 weeks and 1 day ago

In fact I do know how to do it in Windows albeit not with onboard tools.



from the "Sysinternals Suite" at MS.

Then put it into your PATH by going to the System Settings.

([Win]+[Pause]->Advanced->Environment Variables)

Edit PATH, append ";c:\path\to\pssuspend.exe" without the quotes

or try this:

Open a commandline window ([Win]+[R] cmd [Enter])

PATH %PATH%;c:\path\to\pssuspend.exe

which is reset on reboot, or if you have the "setx" program also from MS:

setx PATH %PATH%;c:\path\to\pssuspend.exe

now you can do the following from the cmdline:

pssuspend.exe firefox.exe[Enter] pssuspend.exe -r firefox.exe[Enter]

this should do it.

The above warning concerning Lockups is even more relevant to the windows environment, as the only way to suspend a whole process is to walk all the threads and hold them individually is more risky than holding the process all at once. This is because on Windows there is no atomic operation to do this.

There also is "pausep" out there which i haven't tested but should basically do the same.

Comment by Schneckentreiber 281 weeks ago

Worked for me with chromium browser, which creates multiple processes, with dozens of open tabs:

killall -STOP chromium killall -CONT chromium

(-m is not available for me either)

Comment by alfplayer 218 weeks and 3 days ago

Your point of view

You must be signed in to comment.