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.

### 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.

Hide

### Stay in the loop…

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.

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

May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!
Hide

Hide

Hide

### Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

• » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
• » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

# 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
26
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.

### Alternatives

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

Interesting.

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

Comment by mpb 387 weeks ago

My Firefox suffers from incurable chronic tabitis. :(

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

Comment by Schneckentreiber 385 weeks ago

My recent Jaunty is not allowing -m option.

However following worked, nice command

killall -STOP firefox

killall -CONT firefox

Comment by tejparkash 383 weeks and 1 day ago

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

Comment by mawriz 357 weeks and 5 days ago

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

Get

pssuspend

from the "Sysinternals Suite" at MS.

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

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 357 weeks and 4 days 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 295 weeks ago

### Your point of view

You must be signed in to comment.