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

svn-fast-backup: return value differentiation between serious failure and existing revision?

From: Johannes Graumann <johannes_graumann_at_web.de>
Date: Wed, 24 Mar 2010 09:43:28 +0100

Hi,

I'm scripting the nightly backup of my subversion repositories via 'svn-
fast-backup'. I started out summing up the return values of all invocations
in the script, intending to trigger an email if the sum is != 0, which means
I would have to have a closer look. This strategy is problematic though, as
'svn-fast-backup' also returns 1 if the repository wasn't modified since the
last backup and 'svn-fast-backup' exits with the message that the last
existing revision is already backuped - which is not a "real" problem at
all.
Can anyone point out a strategy on how to distinguish whether 'svn-fast-
backup' shut down for this benign reason or for something serious?

Thanks for any hints, Joh
Received on 2010-03-24 09:44:17 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.