From 46197d986d5da650726e2461ac90348ee75b1176 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Thu, 19 May 2016 23:38:13 +0200 Subject: [PATCH] Fix some typos in the manual --- snapraid.1 | 10 +++++----- snapraid.d | 12 ++++++------ snapraid.txt | 20 ++++++++++---------- 3 files changed, 21 insertions(+), 21 deletions(-) diff --git a/snapraid.1 b/snapraid.1 index 8e6bb2eb..b778ac8d 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -497,7 +497,7 @@ and share the following dirs in the network: .PP to allow remote clients to access all the files at \\\\darkstar\\\\pool. .PP -You may also need to configure remote clients enablinh access at remote +You may also need to configure remote clients enabling access at remote symlinks with the command: .PP .RS 4 @@ -965,7 +965,7 @@ removing possible duplicates. More specifically, if the sub\-second timestamp is not zero, a moved or copied file is identified as such if it matches the name, size and timestamp. If instead the sub\-second timestamp -is zero, it\'s cosidered a copy only if it matches the full path, +is zero, it\'s considered a copy only if it matches the full path, size and timestamp. .PP Note that the second precision timestamp is not modified, @@ -1339,7 +1339,7 @@ The default blocksize is 256 and it should work for most cases. .PP WARNING! This option is for experts only, and it\'s highly recommended to not change it. To change again this value in -future you\'ll have to recreate the whole parity. +future you\'ll have to recreate the whole parity! .PP A reason to use a different hashsize is if you have a lot of small files. In the order of many millions. @@ -1389,7 +1389,7 @@ for most cases. .PP WARNING! This option is for experts only, and it\'s highly recommended to not change it. To change again this value in -future you\'ll have to recreate the whole parity. +future you\'ll have to recreate the whole parity! .PP A reason to use a different hashsize is if your system has small memory. As a rule of thumb SnapRAID usually requires @@ -1624,7 +1624,7 @@ to exclude them you must use a file rule, and not a directory one. .PP If the file name you want to use really contains a \'*\', \'?\', \'[\', or \']\' char, you have to escape it to avoid to have interpreted as a -globbing character. In Unix the escape char is \'\\\' in Windows it\'s \'^\'. +globbing character. In Unix the escape char is \'\\\', in Windows it\'s \'^\'. Note that when the pattern is on the command line, you have to double the escape character to avoid to have it interpreted by the command shell. .PP diff --git a/snapraid.d b/snapraid.d index 2ec81caa..2d30defe 100644 --- a/snapraid.d +++ b/snapraid.d @@ -262,7 +262,7 @@ Getting Started to allow remote clients to access all the files at \\darkstar\\pool. - You may also need to configure remote clients enablinh access at remote + You may also need to configure remote clients enabling access at remote symlinks with the command: :fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1 @@ -302,7 +302,7 @@ Getting Started STEP 1 -> Reconfigure You need some space to recover, even better if you already have an additional disk, but in case, also an external USB or remote disk is enough. - + Change the SnapRAID configuration file to make the "disk" option of the failed disk to point to the place where you have enough empty space to recover the files. @@ -664,7 +664,7 @@ Commands More specifically, if the sub-second timestamp is not zero, a moved or copied file is identified as such if it matches the name, size and timestamp. If instead the sub-second timestamp - is zero, it's cosidered a copy only if it matches the full path, + is zero, it's considered a copy only if it matches the full path, size and timestamp. Note that the second precision timestamp is not modified, @@ -1043,7 +1043,7 @@ Configuration WARNING! This option is for experts only, and it's highly recommended to not change it. To change again this value in - future you'll have to recreate the whole parity. + future you'll have to recreate the whole parity! A reason to use a different hashsize is if you have a lot of small files. In the order of many millions. @@ -1089,7 +1089,7 @@ Configuration WARNING! This option is for experts only, and it's highly recommended to not change it. To change again this value in - future you'll have to recreate the whole parity. + future you'll have to recreate the whole parity! A reason to use a different hashsize is if your system has small memory. As a rule of thumb SnapRAID usually requires @@ -1231,7 +1231,7 @@ Pattern If the file name you want to use really contains a '*', '?', '[', or ']' char, you have to escape it to avoid to have interpreted as a - globbing character. In Unix the escape char is '\' in Windows it's '^'. + globbing character. In Unix the escape char is '\', in Windows it's '^'. Note that when the pattern is on the command line, you have to double the escape character to avoid to have it interpreted by the command shell. diff --git a/snapraid.txt b/snapraid.txt index 72272cbe..eaf12a31 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -279,7 +279,7 @@ and share the following dirs in the network: to allow remote clients to access all the files at \\darkstar\\pool. -You may also need to configure remote clients enablinh access at remote +You may also need to configure remote clients enabling access at remote symlinks with the command: fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1 @@ -720,7 +720,7 @@ removing possible duplicates. More specifically, if the sub-second timestamp is not zero, a moved or copied file is identified as such if it matches the name, size and timestamp. If instead the sub-second timestamp -is zero, it's cosidered a copy only if it matches the full path, +is zero, it's considered a copy only if it matches the full path, size and timestamp. Note that the second precision timestamp is not modified, @@ -1033,18 +1033,18 @@ it doesn't get fragmented, improving the performance. These options are optional and they can be used only one time. -7.3 z-parity FILE ------------------ +7.3 z-parity FILE [,FILE] ... +----------------------------- Defines an alternate file and format to store the triple parity. This option is an alternative at '3-parity' mainly intended for low-end CPUs like ARM or AMD Phenom, Athlon and Opteron that don't -support the SSSE3 instructions set, and in such case it provides +support the SSSE3 instructions set. In such cases it provides a better performance. -This format is similar, but faster, at the one used by the ZFS RAIDZ3, -but it doesn't work beyond triple parity. +This format is similar, but faster, at the one used by the ZFS RAIDZ3. +Like ZFS, it doesn't work beyond triple parity. When using '3-parity' you will be warned if it's recommended to use the 'z-parity' format for a performance improvement. @@ -1123,7 +1123,7 @@ The default blocksize is 256 and it should work for most cases. WARNING! This option is for experts only, and it's highly recommended to not change it. To change again this value in -future you'll have to recreate the whole parity. +future you'll have to recreate the whole parity! A reason to use a different hashsize is if you have a lot of small files. In the order of many millions. @@ -1171,7 +1171,7 @@ for most cases. WARNING! This option is for experts only, and it's highly recommended to not change it. To change again this value in -future you'll have to recreate the whole parity. +future you'll have to recreate the whole parity! A reason to use a different hashsize is if your system has small memory. As a rule of thumb SnapRAID usually requires @@ -1326,7 +1326,7 @@ to exclude them you must use a file rule, and not a directory one. If the file name you want to use really contains a '*', '?', '[', or ']' char, you have to escape it to avoid to have interpreted as a -globbing character. In Unix the escape char is '\' in Windows it's '^'. +globbing character. In Unix the escape char is '\', in Windows it's '^'. Note that when the pattern is on the command line, you have to double the escape character to avoid to have it interpreted by the command shell.