Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to automate an svnadmin dump command for a backup script, and I want to do something like this:

find /var/svn/* \( ! -name dir -prune \) -type d -exec svnadmin dump {} > {}.svn \;

This seems to work, in that it looks through each svn repository in /var/svn, and runs svnadmin dump on it.

However, the second {} in the exec command doesn't get substituted for the name of the directory being processed. It basically just results a single file named {}.svn.

I suspect that this is because the shell interprets > to end the find command, and it tries redirecting stdout from that command to the file named {}.svn.

Any ideas?

share|improve this question
up vote 23 down vote accepted

You can do the redirection like this:

find /var/svn/* \( ! -name dir -prune \) -type d -exec sh -c 'svnadmin dump {} > {}.svn' \;

and the correct substitution will be done.

share|improve this answer

No, however you can write a simple bash script to do that then call it from find.
Example (/tmp/dump.sh):

#!/bin/sh
svn admin dump "$1" > "$1".svn

then:

find /var/svn/* \( ! -name dir -prune \) -type d -exec sh /tmp/dump.sh '{}' \;
share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .