New feature:

- Bootup sequence prevention implemented.

Touched the docs up:
This commit is contained in:
vorotamoroz
2021-12-28 11:30:19 +09:00
parent 55545da45f
commit c3464a4e9c
11 changed files with 109 additions and 12 deletions
+5 -2
View File
@@ -212,8 +212,11 @@ The remote database indicates that has been unlocked Pattern 1.
When you mark all devices as resolved, you can unlock the database.
But, there's no problem even if you leave it as it is.
### Reread all files
Reread all files in the vault, and update them into the database if there's diff or could not read from the database.
### Verify and repair all files
read all files in the vault, and update them into the database if there's diff or could not read from the database.
### Sanity check
Make sure that all the files on the local database have all chunks.
### Drop history
Drop all histories on the local database and the remote database, and initialize When synchronization time has been prolonged to the new device or new vault, or database size became to be much larger. Try this.