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



list files by testing the ownership

Terminal - list files by testing the ownership
find . -user root
2013-10-16 08:08:41
User: jedifu
Functions: continue echo find read
list files by testing the ownership

Alternative to mnikhil's ls/awk solution


There are 3 alternatives - vote for the best!

Terminal - Alternatives
read -N1
2013-10-10 10:09:43
User: totti
Functions: read
Tags: read user

Usage exaple cmd

echo 'Sure to continue ??'; read -n1 choi; if [ "$choi" = 'y' ] || [ "$choi" = 'Y' ]; then echo -e '\nExecuting..'; else echo 'Aborted'; fi
ls -la | awk '$3 == "oracle" || $3 == "root" {print $9}'

Know a better way?

If you can do better, submit your command here.

What others think

That will not only list "files" but directories, etc. Its somewhat a limitation of the shell (in this case I assume bash) to have to resort to using an external command for such a simple operation, all we want is a pattern (similar to any glob). zshell's "glob qualifiers" offer a means to pass such a pattern:

print -rl *(.u0N) # root/uid 0 owned "files"

print -rl *(Du0N) # root/uid 0 owned "directories"

print -rl *(.u1000f:u+x:N) # list files owned by uid 1000 that have execute bit set. Note that the 'N' sets a 'NULL_GLOB' so that a not match is empty.

Comment by khayyam 78 weeks and 1 day ago

Your point of view

You must be signed in to comment.