From 44214e03cb274f597c325b97bb7664ae4ff9f9fb Mon Sep 17 00:00:00 2001 From: bescoto Date: Thu, 15 Dec 2005 06:12:54 +0000 Subject: strengthened pid error message git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@710 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109 --- rdiff-backup/rdiff_backup/regress.py | 7 ++++--- 1 file 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,)) - -- cgit v1.2.1