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.

Universal configuration monitoring and system of record for IT.
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

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

Top Tags

Hide

Functions

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

count processes with status "D" uninterruptible sleep

Terminal - count processes with status "D" uninterruptible sleep
top -b -n 1 | awk '{if (NR <=7) print; else if ($8 == "D") {print; count++} } END {print "Total status D: "count}'
2009-02-19 21:14:46
User: jcgam69
Functions: awk top
4
count processes with status "D" uninterruptible sleep

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
ps axu | awk '{if (NR <=7) print; else if ($8 == "D") {print; count++} } END {print "Total status D: "count}'
ps -eo stat= | sort | uniq -c | sort -n
2011-03-25 13:01:42
User: fossilet
Functions: ps sort uniq
0

Use ps instead of top. But do not use BSD options at all, they are confusing.

Use "s=" or "state=" to show consice process statuses.

Know a better way?

If you can do better, submit your command here.

What others think

Alright smart guy, how would I create said uninterruptible sleeping process?

Vote up BTW

Comment by Williebee 406 weeks and 1 day ago

Pull the plug on an NFS server. Processes that attempt to read from the NFS file system will block in state "D" until the NFS server returns, or the system is rebooted. (Blatantly plagiarized from the web because I didn't know either).

Comment by jcgam69 406 weeks ago

I'm not quite getting this awk. You want to always print the first seven lines of output regardless of the state? Also you don't want to know if the state *IS* D, but you want to know if it contains D. This would be fixed with:

awk '$8 ~ /D/{print}'
Comment by wxl 53 weeks and 2 days ago

I'm not quite getting this awk. You want to always print the first seven lines of output regardless of the state? Also you don't want to know if the state *IS* D, but you want to know if it contains D. This would be fixed with:

awk '$8 ~ /D/{print}'
Comment by wxl 53 weeks and 2 days ago

oops error with the server and i can't delete. boo.

Comment by wxl 53 weeks and 2 days ago

Your point of view

You must be signed in to comment.