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
49dfbcb8
Commit
49dfbcb8
authored
19 years ago
by
intrigeri
Browse files
Options
Downloads
Patches
Plain Diff
Added a few safety checks to pgsql handler.
parent
4e0c31d0
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
changelog
+4
-0
4 additions, 0 deletions
changelog
handlers/pgsql
+34
-11
34 additions, 11 deletions
handlers/pgsql
with
38 additions
and
11 deletions
changelog
+
4
−
0
View file @
49dfbcb8
...
...
@@ -16,6 +16,10 @@ version XX -- ...
make use of configurable $VSERVERINFO instead of hard-coded vserver-info.
fixed dpkg existence test inside vserver.
fixed $nodpkg use.
changes to pgsql handler
now checks if the specified vserver is running.
now checks if $PGSQLDUMP/$PGSQLDUMPALL are available where needed.
now checks if "postgres" user exists on the host/vserver.
version 0.7 -- July 26 2005
added ninjahelper: a dialog based wizard for creating backupninja configs.
...
...
This diff is collapsed.
Click to expand it.
handlers/pgsql
+
34
−
11
View file @
49dfbcb8
...
...
@@ -11,33 +11,56 @@ localhost=`hostname`
# If vservers are configured, decide if the handler should
# use them or if it should just operate on the host
if [ "$vservers" == "yes" ]
then
if [ ! -z $vsname ]
then
info "Using vserver '$vsname'"
if [ "$vservers" == "yes" ]; then
if [ ! -z $vsname ]; then
info "using vserver '$vsname'"
usevserver=1
else
info "
N
o vserver name specified, actions will be performed on the host"
info "
n
o vserver name specified, actions will be performed on the host"
fi
fi
# Check to make sure that the specified vserver exists
if [ $usevserver ]
then
# As needed, make sure that :
# * the specified vserver exists and is running
# * the specified vserver or host has the needed executables
if [ $usevserver ]; then
info "examining vserver '$vsname'"
# does it exist ?
vroot="$VROOTDIR/$vsname"
[ -d $vroot ] || fatal "vserver '$vsname' does not exist at '$vroot'"
# is it running ?
running=`$VSERVERINFO $vsname RUNNING`
if [ $running = 1 ]; then
if [ "$databases" == "all" ]; then
[ -x "$vroot`$VSERVER $vsname exec which $PGSQLDUMPALL`" ] || \
fatal "Can't find $PGSQLDUMPALL in vserver $vsname."
else
[ -x "$vroot`$VSERVER $vsname exec which $PGSQLDUMP`" ] || \
fatal "Can't find $PGSQLDUMP in vserver $vsname."
fi
else
fatal "vserver $vsname is not running."
fi
else
if [ "$databases" == "all" ]; then
[ -x "`which $PGSQLDUMPALL`" ] || \
fatal "Can't find $PGSQLDUMPALL."
else
[ -x "`which $PGSQLDUMP`" ] || \
fatal "Can't find $PGSQLDUMP."
fi
fi
# create backup dir, the vroot variable will be empty if no vsname was specified
# and will proceed to operate on the host
[ -d $vroot$backupdir ] || mkdir -p $vroot$backupdir
[ -d $vroot$backupdir ] ||
(debug "
mkdir -p $vroot$backupdir
"; mkdir -p $vroot$backupdir)
[ -d $vroot$backupdir ] || fatal "Backup directory '$vroot$backupdir'"
# give backup dir the good uid and permissions
# (in respect to the vserver, if $usevserver)
pguid=`grep '^postgres:' $vroot/etc/passwd | awk -F: '{print $3}'`
[ -n "$pguid" ] || \
fatal "No user called postgres`[ $usevserver != 1 ] || echo \" on vserver $vsname\"`."
debug "chown $pguid $vroot$backupdir"
chown $pguid $vroot$backupdir
debug "chmod 700 $vroot$backupdir"
...
...
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