[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnadmin verify

From: KM <info4km_at_yahoo.com>
Date: 2007-04-25 15:05:19 CEST

  you are correct about svnadmin verify. It only tells you if there is corruption. A successfull verification seems to return 0 and an invalid verification a non-zero (usually 1) - as with most unix commands. You can test this easily. Make a copy of your repository with a new name like test. Corrupt a file and run svnadmin verify and test $?.
  Hope this helps

Mark Clements <gmane@kennel17.co.uk> wrote:

I have often seen it advised that you run svnadmin verify as part of your
backup script. As far as I can see this command doesn't actually make any
changes at all (i.e. it doesn't fix problems), it just tells you if there is
anything 'funny' going on in your repository.

Is this correct?

If so what return value should I be looking for to signify that there was an
error in the repository, and what string should I grep the output for, so
that my cron job only e-mails me when an error occurs (by default each
revision is output to the screen, so I need to supress all the successful

(Or if I have misunderstood what svnadmin verify does then please enlighten

- Mark Clements

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.
Received on Wed Apr 25 15:05:52 2007

This is an archived mail posted to the Subversion Users mailing list.