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.

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



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

Archive all SVN repositories in platform indepenent form

Terminal - Archive all SVN repositories in platform indepenent form
find repMainPath -maxdepth 1 -mindepth 1 -type d | while read dir; do echo processing $dir; sudo svnadmin dump --deltas $dir >dumpPath/`basename $dir`; done
2009-09-15 20:14:51
User: Marco
Functions: dump echo find read sudo
Archive all SVN repositories in platform indepenent form

This command dumps all SVN repositories inside of folder "repMainPath" (not recursively) to the folder "dumpPath", where one dump file will be created for each SVN repository.


There is 1 alternative - vote for the best!

Terminal - Alternatives
budir=/tmp/bu.$$;for name in repMainPath/*/format;do dir=${name%/format};bufil=dumpPath/${dir##*/};svnadmin hotcopy --clean-logs $dir $budir;svnadmin dump --delta $budir>$bufil;rm -rf $budir;done
2009-09-16 01:34:48
User: arcege
Functions: dump
Tags: bash svn

Use of hotcopy for safety/stability of the backups.

Know a better way?

If you can do better, submit your command here.

What others think

Recreate the dumps:

find dumpPath -type f | while read file; do echo processing $file; mkdir repMainPath/`basename $file`; svnadmin create repMainPath/`basename $file`; svnadmin load repMainPath`basename $file` <$file; done
Comment by Marco 405 weeks and 5 days ago

I just use fsfs for my storage. Problem solved... on so many levels. BDB is awful.

Comment by linuxrawkstar 405 weeks and 5 days ago

Just make a "normal" copy of an fsfs SVN backend for backup purpose is not recommended by svnbook. You have to make sure, that no access is done during copy and copying the fsfs-folderstructure has to be executed in a special sequence.

All this is automatically considered by svn's hotcopy or dump commands.

Comment by Marco 405 weeks and 5 days ago

Unfortunately, for large repositories, dump can take time. At this time of global development, there are fewer times of downtime. Hotcopy is a lot faster and the dump can be taken offline from the copy with shorter locks on the master repository.

Comment by arcege 405 weeks and 4 days ago

That's right. Hotcopy is much faster than dump. But the hotcopy operation generates a copy of the database. But this copy may only be readable by the same version of SVN. This may be okay for "short term backups".

On the other hand, the dump operation, dumps the whole database into a version independent format. A format which is guaranteed by the SVN development team to not change in future anymore. So this can be used for "long term backups".

Refer to: http://svn.haxx.se/users/archive-2005-05/0842.shtml

Comment by Marco 355 weeks and 4 days ago

Your point of view

You must be signed in to comment.