Make it clear what lockfile could not be acquired.

This commit is contained in:
intrigeri 2012-06-11 15:54:31 +02:00
parent b05065625c
commit 7af82be3ec
2 changed files with 3 additions and 1 deletions

View File

@ -3,6 +3,8 @@ version 1.0 -- UNRELEASED
mysql: mysql:
. Use --skip-events when backing up the performance_schema database. . Use --skip-events when backing up the performance_schema database.
(Closes: #673572) (Closes: #673572)
backupninja changes
. Make it clear what lockfile could not be acquired, if any.
version 1.0-rc1 -- May 15, 2012 version 1.0-rc1 -- May 15, 2012
handler changes handler changes

View File

@ -349,7 +349,7 @@ function process_action() {
else else
# a backup is probably ongoing already, so display an error message # 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 echo "Fatal: Could not acquire lock $lockfile. A backup is probably already running for $file." >>$bufferfile
fi fi
} 200> $lockfile } 200> $lockfile