mirror of
https://github.com/vmstan/gravity-sync.git
synced 2024-08-30 18:22:11 +00:00
s/insure/ensure (#91)
This commit is contained in:
parent
9a420994d3
commit
8d5c725d0c
@ -104,7 +104,7 @@ The default command for Gravity Sync is simple.
|
||||
|
||||
But you can also run `./gravity-sync.sh smart` if you feel like it, and it'll do the same thing.
|
||||
|
||||
Gravity Sync will perform some checks to help insure success and then stop before making changes if it detects an issue. It will also perform the same `compare` function outlined above, and if there are no changes pending, it will exit without making an attempt to copy data.
|
||||
Gravity Sync will perform some checks to help ensure success and then stop before making changes if it detects an issue. It will also perform the same `compare` function outlined above, and if there are no changes pending, it will exit without making an attempt to copy data.
|
||||
|
||||
**Example:** If the `gravity.db` has been modified on the primary Pi-hole, but the `custom.list` file has been changed on the secondary, Gravity Sync will now do a pull of the `gravity.db` then push `custom.list` and finally restart the correct components on each server. It will also now only perform a sync of each component if there are changes within each type to replicate. So if you only make a small change to your Local DNS settings, it doesn't kickoff the larger `gravity.db` replication.
|
||||
|
||||
|
@ -1137,7 +1137,7 @@ function detect_remotersync {
|
||||
CMD_REQUESTED="touch ~/gs.test"
|
||||
create_sshcmd
|
||||
|
||||
MESSAGE="If pull test fails insure RSYNC is installed on ${REMOTE_HOST}"
|
||||
MESSAGE="If pull test fails ensure RSYNC is installed on ${REMOTE_HOST}"
|
||||
echo_warn
|
||||
|
||||
MESSAGE="Pulling Test File to $HOSTNAME"
|
||||
|
Loading…
Reference in New Issue
Block a user