clarify behaviour of backup command

from RobSlgm, issue #172
This commit is contained in:
Mechiel Lukkien 2024-05-09 17:48:22 +02:00
parent 83004bb18e
commit 1fc8f165f7
No known key found for this signature in database
2 changed files with 12 additions and 4 deletions

8
doc.go
View file

@ -825,8 +825,12 @@ All files in the data directory that aren't recognized (i.e. other than known
database files, message files, an acme directory, the "tmp" directory, etc),
are stored, but with a warning.
A clean successful backup does not print any output by default. Use the
-verbose flag for details, including timing.
Remove files in the destination directory before doing another backup. The
backup command will not overwrite files, but print and return errors.
Exit code 0 indicates the backup was successful. A clean successful backup does
not print any output, but may print warnings. Use the -verbose flag for
details, including timing.
To restore a backup, first shut down mox, move away the old data directory and
move an earlier backed up directory in its place, run "mox verifydata",

View file

@ -1367,8 +1367,12 @@ All files in the data directory that aren't recognized (i.e. other than known
database files, message files, an acme directory, the "tmp" directory, etc),
are stored, but with a warning.
A clean successful backup does not print any output by default. Use the
-verbose flag for details, including timing.
Remove files in the destination directory before doing another backup. The
backup command will not overwrite files, but print and return errors.
Exit code 0 indicates the backup was successful. A clean successful backup does
not print any output, but may print warnings. Use the -verbose flag for
details, including timing.
To restore a backup, first shut down mox, move away the old data directory and
move an earlier backed up directory in its place, run "mox verifydata",