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:



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!

Top Tags



Find broken symlinks

Terminal - Find broken symlinks
find -L . -type l
2011-04-08 07:52:28
User: depesz
Functions: find
Find broken symlinks


There are 2 alternatives - vote for the best!

Terminal - Alternatives
find . -type l -xtype l
2012-05-15 08:24:47
Functions: find
Tags: find symlinks

This is much safer than using -L, because it will not follow links that point to places outside the target directory subtree (CWD, in this case). See here for explanation: http://unix.stackexchange.com/a/38691/9382

find /path/to/search -xtype l
2012-09-29 13:40:26
User: pooryorick
Functions: find

To understand why this is the equivalent of "find -L /path/to/search -type l, see http://ynform.org/w/Pub/FindBrokenSymbolicLinks or look at http://www.gnu.org/software/findutils/manual/html_mono/find.html

find . -type l | xargs file | grep broken

Know a better way?

If you can do better, submit your command here.

What others think

Remember guys, search is your friend.

This is a duplicate of:




Comment by flatcap 267 weeks and 4 days ago

I found an old better alternative as well:


The "find -L" solution will follow valid links and possibly search huge directories elsewhere making the search slow. Solution 954 works well by just searching the desired directory structure and just reporting the broken links within that.

Comment by quadcore 267 weeks and 1 day ago

Your point of view

You must be signed in to comment.