summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-12-15 06:12:54 +0000
committerbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-12-15 06:12:54 +0000
commit44214e03cb274f597c325b97bb7664ae4ff9f9fb (patch)
tree4539ab051202ed7276a00f94c52ad507348ba0e9
parent387ea7be65f0e34b1441d1d4a6975e2445f6bf4a (diff)
downloadrdiff-backup-44214e03cb274f597c325b97bb7664ae4ff9f9fb.tar.gz
strengthened pid error message
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@710 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
-rw-r--r--rdiff-backup/rdiff_backup/regress.py7
1 files changed, 4 insertions, 3 deletions
diff --git a/rdiff-backup/rdiff_backup/regress.py b/rdiff-backup/rdiff_backup/regress.py
index 0ef6e57..9f4b925 100644
--- a/rdiff-backup/rdiff_backup/regress.py
+++ b/rdiff-backup/rdiff_backup/regress.py
@@ -353,7 +353,8 @@ def check_pids(curmir_incs):
pid = extract_pid(curmir_rp)
if pid is not None and pid_running(pid):
log.Log.FatalError(
-"""It appears that a previous rdiff-backup session with process id
-%d is still running. To proceed with regress, rerun rdiff-backup with the
+"""It appears that a previous rdiff-backup session with process
+id %d is still running. If two different rdiff-backup processes write
+the same repository simultaneously, data corruption will probably
+result. To proceed with regress anyway, rerun rdiff-backup with the
--force option.""" % (pid,))
-