From b8628879a26f189c53535c0cdd1a65287a5b9cfa Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Tue, 1 Mar 2016 22:32:15 +0100 Subject: [PATCH] Auto update --- faq.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/faq.html b/faq.html index 1c195193..3a873b93 100644 --- a/faq.html +++ b/faq.html @@ -1092,7 +1092,7 @@ It's created where the first content file is placed.

What's the notice about zero sub-second timestamp?

-In the status command you may now get a notice like: +In the 'status' command you may now get a notice like: 

 You have XXXXX files with zero sub-second timestamp.
@@ -1101,8 +1101,8 @@ Run the 'touch' command to set it to a not zero value.
 

 It means that a number of your files have a timestamp approximated at the second value,
 when instead your filesystem can store a more precise timestamp, with a sub-second precision.
-This is not a problem by itself, but it could limit the SnapRAID effectiviness when detecting
-moved or copied files.
+This is not a problem by itself, but it could limit the SnapRAID effectiviness to detect
+moved or copied files between different disks.
 You have the option to set that subsecond timestamp to a random value using the new 'touch' command.
 Note that the second part of the timestamp is not modified.