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:
i'm using gawk, you may get varying mileage with other varieties. You might want to change the / after du to say, /home/ or /var or something, otherwise this command might take quite some time to complete. Sorry it's so obsfucated, I had to turn a script into a one-liner under 255 characters for commandlinefu. Note: the bar ratio is relative, so the highest ratio of the total disk, "anchors" the rest of the graph. EDIT: the math was slightly wrong, fixed it. Also, made it compliant with older versions of df.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Getting this error.
du: warning: summarising conflicts with --max-depth=1
Not sure why that would happen. According to the du source code, that should only happen:
if (opt_summarize_only && max_depth_specified && max_depth != 0)
and unless you added a max-depth=0, or -s, i'm not sure why it would give you that error. I'm curios, what version of du are you running, and what OS ?
Ubuntu 10.10 x64
du (GNU coreutils) 8.5
Cheers
what happens when you run:
sudo du / --max-depth=1|sort -rn -k1
Same thing bud :|
Got it right!
Thanks
"for (a=0;ac){c=a}}" this loop is completely useless (and also responsable of the slowness of your command since a can be very large)
substitute it with a=$1; if (a>c){c=a}