From 7af82be3ecf950fd19190d06fb9ad0f3f0aca97a Mon Sep 17 00:00:00 2001
From: intrigeri <intrigeri@boum.org>
Date: Mon, 11 Jun 2012 15:54:31 +0200
Subject: [PATCH] Make it clear what lockfile could not be acquired.
---
ChangeLog | 2 ++
src/backupninja.in | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index f2c9270..faf06dd 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -3,6 +3,8 @@ version 1.0 -- UNRELEASED
mysql:
. Use --skip-events when backing up the performance_schema database.
(Closes: #673572)
+ backupninja changes
+ . Make it clear what lockfile could not be acquired, if any.
version 1.0-rc1 -- May 15, 2012
handler changes
diff --git a/src/backupninja.in b/src/backupninja.in
index 0400828..0f74906 100755
--- a/src/backupninja.in
+++ b/src/backupninja.in
@@ -349,7 +349,7 @@ function process_action() {
else
# a backup is probably ongoing already, so display an error message
- debug "failed to acquire lock"
+ debug "failed to acquire lock $lockfile"
echo "Fatal: Could not acquire lock $lockfile. A backup is probably already running for $file." >>$bufferfile
fi
} 200> $lockfile
--
GitLab