diff options
author | DL6ER <dl6er@dl6er.de> | 2021-12-22 21:53:52 +0300 |
---|---|---|
committer | DL6ER <dl6er@dl6er.de> | 2021-12-22 21:53:52 +0300 |
commit | d2a98ae95498d6f72d0b1ceee3d46ec2e7ecfe4c (patch) | |
tree | e02e9624762e9eeed0648f35885c0069565b4ef2 /gravity.sh | |
parent | 2e1ce7fc87a5934c9316db1ce1824ac0e3636dcd (diff) |
Document -r recover force case
Signed-off-by: DL6ER <dl6er@dl6er.de>
Diffstat (limited to 'gravity.sh')
-rwxr-xr-x | gravity.sh | 23 |
1 files changed, 15 insertions, 8 deletions
@@ -909,14 +909,21 @@ repairSelector() { Attempt to repair gravity database Available options: - pihole -g -r recover Try to recover a damaged gravity database file. - Pi-hole tries to restore as much as possible - from a corrupted gravity database. - pihole -g -r recreate Create a new gravity database file from scratch. - This will remove your existing gravity database - and create a new file from scratch. If you still - have the migration backup created when migrating - to Pi-hole v5.0, Pi-hole will import these files." + pihole -g -r recover Try to recover a damaged gravity database file. + Pi-hole tries to restore as much as possible + from a corrupted gravity database. + + pihole -g -r recover force Pi-hole will run the recovery process even when + no damage is detected. This option is meant to be + a last resort. Recovery is a fragile task + consuming a lot of resources and shouldn't be + performed unnecessarily. + + pihole -g -r recreate Create a new gravity database file from scratch. + This will remove your existing gravity database + and create a new file from scratch. If you still + have the migration backup created when migrating + to Pi-hole v5.0, Pi-hole will import these files." exit 0;; esac } |