Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
backupninja
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
lyz
backupninja
Commits
7af82be3
Commit
7af82be3
authored
12 years ago
by
intrigeri
Browse files
Options
Downloads
Patches
Plain Diff
Make it clear what lockfile could not be acquired.
parent
b0506562
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
ChangeLog
+2
-0
2 additions, 0 deletions
ChangeLog
src/backupninja.in
+1
-1
1 addition, 1 deletion
src/backupninja.in
with
3 additions
and
1 deletion
ChangeLog
+
2
−
0
View file @
7af82be3
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
src/backupninja.in
+
1
−
1
View file @
7af82be3
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment