Remove groffisms from the man page.  This changes "\(dq" to a double-quote

character ("), "\(cq" to a single-quote character ('), and eliminates the

use of "\&" except where it's needed at the beginning of the line.

@@ -20,7 +20,7 @@

 .PP 

 The file consists of modules and parameters. A module begins with the

 name of the module in square brackets and continues until the next

-module begins. Modules contain parameters of the form \(dq\&name = value\(dq\&.

+module begins. Modules contain parameters of the form "name = value".

 .PP 

 The file is line\-based \-\- that is, each newline\-terminated line represents

 either a comment, a module name or a parameter.

@@ -33,9 +33,9 @@

 .PP 

 Any line \fBbeginning\fP with a hash (#) is ignored, as are lines containing

 only whitespace. (If a hash occurs after anything other than leading

-whitespace, it is considered a part of the line\(cq\&s content.)

+whitespace, it is considered a part of the line's content.)

 .PP 

-Any line ending in a \e is \(dq\&continued\(dq\& on the next line in the

+Any line ending in a \e is "continued" on the next line in the

 customary UNIX fashion.

 .PP 

 The values following the equals sign in parameters are all either a string

@@ -56,7 +56,7 @@

 .PP 

 You can launch it either via inetd, as a stand\-alone daemon, or from

 an rsync client via a remote shell.  If run as a stand\-alone daemon then

-just run the command \(dq\&\fBrsync \-\-daemon\fP\(dq\& from a suitable startup script.

+just run the command "\fBrsync \-\-daemon\fP" from a suitable startup script.

 .PP 

 When run via inetd you should add a line like this to /etc/services:

 .PP 

@@ -72,7 +72,7 @@

 .fi 

 .PP 

-Replace \(dq\&/usr/bin/rsync\(dq\& with the path to where you have rsync installed on

+Replace "/usr/bin/rsync" with the path to where you have rsync installed on

 your system.  You will then need to send inetd a HUP signal to tell it to

 reread its config file.

 .PP 

@@ -104,7 +104,7 @@

 .PP 

 .IP "\fBmotd file\fP"

 This parameter allows you to specify a

-\(dq\&message of the day\(dq\& to display to clients on each connect. This

+"message of the day" to display to clients on each connect. This

 usually contains site information and any legal notices. The default

 is no motd file.

 This can be overridden by the \fB\-\-dparam=motdfile=FILE\fP

@@ -163,14 +163,14 @@

 of available modules. The default is no comment.

 .IP 

 .IP "\fBpath\fP"

-This parameter specifies the directory in the daemon\(cq\&s

+This parameter specifies the directory in the daemon's

 filesystem to make available in this module.  You must specify this parameter

 for each module in \f(CWrsyncd.conf\fP.

 .IP 

-You may base the path\(cq\&s value off of an environment variable by surrounding

+You may base the path's value off of an environment variable by surrounding

 the variable name with percent signs.  You can even reference a variable

 that is set by rsync when the user connects.

-For example, this would use the authorizing user\(cq\&s name in the path:

+For example, this would use the authorizing user's name in the path:

 .IP 

 .nf 

     path = /home/%RSYNC_USER_NAME% 

 .IP 

 It is fine if the path includes internal spaces \-\- they will be retained

-verbatim (which means that you shouldn\(cq\&t try to escape them).  If your final

+verbatim (which means that you shouldn't try to escape them).  If your final

 directory has a trailing space (and this is somehow not something you wish to

 fix), append a trailing slash to the path to avoid losing the trailing

 whitespace.

 .IP 

 .IP "\fBuse chroot\fP"

-If \(dq\&use chroot\(dq\& is true, the rsync daemon will chroot

-to the \(dq\&path\(dq\& before starting the file transfer with the client.  This has

+If "use chroot" is true, the rsync daemon will chroot

+to the "path" before starting the file transfer with the client.  This has

 the advantage of extra protection against possible implementation security

 holes, but it has the disadvantages of requiring super\-user privileges,

 of not being able to follow symbolic links that are either absolute or outside

 of the new root path, and of complicating the preservation of users and groups

 by name (see below).

 .IP 

-As an additional safety feature, you can specify a dot\-dir in the module\(cq\&s

-\(dq\&path\(dq\& to indicate the point where the chroot should occur.  This allows rsync

-to run in a chroot with a non\-\(dq\&/\(dq\& path for the top of the transfer hierarchy.

+As an additional safety feature, you can specify a dot\-dir in the module's

+"path" to indicate the point where the chroot should occur.  This allows rsync

+to run in a chroot with a non\-"/" path for the top of the transfer hierarchy.

 Doing this guards against unintended library loading (since those absolute

 paths will not be inside the transfer hierarchy unless you have used an unwise

 pathname), and lets you setup libraries for the chroot that are outside of the

-transfer.  For example, specifying \(dq\&/var/rsync/./module1\(dq\& will chroot to the

-\(dq\&/var/rsync\(dq\& directory and set the inside\-chroot path to \(dq\&/module1\(dq\&.  If you

+transfer.  For example, specifying "/var/rsync/./module1" will chroot to the

+"/var/rsync" directory and set the inside\-chroot path to "/module1".  If you

 had omitted the dot\-dir, the chroot would have used the whole path, and the

-inside\-chroot path would have been \(dq\&/\(dq\&.

+inside\-chroot path would have been "/".

 .IP 

-When \(dq\&use chroot\(dq\& is false or the inside\-chroot path is not \(dq\&/\(dq\&, rsync will:

+When "use chroot" is false or the inside\-chroot path is not "/", rsync will:

 (1) munge symlinks by

-default for security reasons (see \(dq\&munge symlinks\(dq\& for a way to turn this

+default for security reasons (see "munge symlinks" for a way to turn this

 off, but only if you trust your users), (2) substitute leading slashes in

-absolute paths with the module\(cq\&s path (so that options such as

+absolute paths with the module's path (so that options such as

 \fB\-\-backup\-dir\fP, \fB\-\-compare\-dest\fP, etc. interpret an absolute path as

-rooted in the module\(cq\&s \(dq\&path\(dq\& dir), and (3) trim \(dq\&..\(dq\& path elements from

+rooted in the module's "path" dir), and (3) trim ".." path elements from

 args if rsync believes they would escape the module hierarchy.

-The default for \(dq\&use chroot\(dq\& is true, and is the safer choice (especially

+The default for "use chroot" is true, and is the safer choice (especially

 if the module is not read\-only).

 .IP 

 When this parameter is enabled, rsync will not attempt to map users and groups

@@ -231,12 +231,12 @@

 used by these library functions (traditionally /etc/passwd and

 /etc/group, but perhaps additional dynamic libraries as well).

 .IP 

-If you copy the necessary resources into the module\(cq\&s chroot area, you

-should protect them through your OS\(cq\&s normal user/group or ACL settings (to

-prevent the rsync module\(cq\&s user from being able to change them), and then

-hide them from the user\(cq\&s view via \(dq\&exclude\(dq\& (see how in the discussion of

+If you copy the necessary resources into the module's chroot area, you

+should protect them through your OS's normal user/group or ACL settings (to

+prevent the rsync module's user from being able to change them), and then

+hide them from the user's view via "exclude" (see how in the discussion of

 that parameter).  At that point it will be safe to enable the mapping of users

-and groups by name using the \(dq\&numeric ids\(dq\& daemon parameter (see below).

+and groups by name using the "numeric ids" daemon parameter (see below).

 .IP 

 Note also that you are free to setup custom user/group information in the

 chroot area that is different from your normal system.  For example, you

@@ -250,7 +250,7 @@

 the \fB\-\-numeric\-ids\fP command\-line option.  By default, this parameter is

 enabled for chroot modules and disabled for non\-chroot modules.

 .IP 

-A chroot\-enabled module should not have this parameter enabled unless you\(cq\&ve

+A chroot\-enabled module should not have this parameter enabled unless you've

 taken steps to ensure that the module has the necessary resources it needs

 to translate names, and that it is not possible for a user to change those

 resources.

@@ -260,52 +260,52 @@

 all symlinks in the same way as the (non\-daemon\-affecting)

 \fB\-\-munge\-links\fP command\-line option (using a method described below).

 This should help protect your files from user trickery when

-your daemon module is writable.  The default is disabled when \(dq\&use chroot\(dq\&

-is on and the inside\-chroot path is \(dq\&/\(dq\&, otherwise it is enabled.

+your daemon module is writable.  The default is disabled when "use chroot"

+is on and the inside\-chroot path is "/", otherwise it is enabled.

 .IP 

 If you disable this parameter on a daemon that is not read\-only, there

 are tricks that a user can play with uploaded symlinks to access

-daemon\-excluded items (if your module has any), and, if \(dq\&use chroot\(dq\&

+daemon\-excluded items (if your module has any), and, if "use chroot"

 is off, rsync can even be tricked into showing or changing data that

-is outside the module\(cq\&s path (as access\-permissions allow).

+is outside the module's path (as access\-permissions allow).

 .IP 

 The way rsync disables the use of symlinks is to prefix each one with

-the string \(dq\&/rsyncd\-munged/\(dq\&.  This prevents the links from being used

+the string "/rsyncd\-munged/".  This prevents the links from being used

 as long as that directory does not exist.  When this parameter is enabled,

 rsync will refuse to run if that path is a directory or a symlink to

-a directory.  When using the \(dq\&munge symlinks\(dq\& parameter in a chroot area

-that has an inside\-chroot path of \(dq\&/\(dq\&, you should add \(dq\&/rsyncd\-munged/\(dq\&

+a directory.  When using the "munge symlinks" parameter in a chroot area

+that has an inside\-chroot path of "/", you should add "/rsyncd\-munged/"

 to the exclude setting for the module so that

-a user can\(cq\&t try to create it.

+a user can't try to create it.

 .IP 

 Note:  rsync makes no attempt to verify that any pre\-existing symlinks in

-the module\(cq\&s hierarchy are as safe as you want them to be (unless, of

+the module's hierarchy are as safe as you want them to be (unless, of

 course, it just copied in the whole hierarchy).  If you setup an rsync

 daemon on a new area or locally add symlinks, you can manually protect your

-symlinks from being abused by prefixing \(dq\&/rsyncd\-munged/\(dq\& to the start of

-every symlink\(cq\&s value.  There is a perl script in the support directory

-of the source code named \(dq\&munge\-symlinks\(dq\& that can be used to add or remove

+symlinks from being abused by prefixing "/rsyncd\-munged/" to the start of

+every symlink's value.  There is a perl script in the support directory

+of the source code named "munge\-symlinks" that can be used to add or remove

 this prefix from your symlinks.

 .IP 

-When this parameter is disabled on a writable module and \(dq\&use chroot\(dq\& is off

-(or the inside\-chroot path is not \(dq\&/\(dq\&),

-incoming symlinks will be modified to drop a leading slash and to remove \(dq\&..\(dq\&

-path elements that rsync believes will allow a symlink to escape the module\(cq\&s

+When this parameter is disabled on a writable module and "use chroot" is off

+(or the inside\-chroot path is not "/"),

+incoming symlinks will be modified to drop a leading slash and to remove ".."

+path elements that rsync believes will allow a symlink to escape the module's

 hierarchy.  There are tricky ways to work around this, though, so you had

 better trust your users if you choose this combination of parameters.

 .IP 

 .IP "\fBcharset\fP"

 This specifies the name of the character set in which the

-module\(cq\&s filenames are stored.  If the client uses an \fB\-\-iconv\fP option,

-the daemon will use the value of the \(dq\&charset\(dq\& parameter regardless of the

+module's filenames are stored.  If the client uses an \fB\-\-iconv\fP option,

+the daemon will use the value of the "charset" parameter regardless of the

 character set the client actually passed.  This allows the daemon to

 support charset conversion in a chroot module without extra files in the

 chroot area, and also ensures that name\-translation is done in a consistent

-manner.  If the \(dq\&charset\(dq\& parameter is not set, the \fB\-\-iconv\fP option is

-refused, just as if \(dq\&iconv\(dq\& had been specified via \(dq\&refuse options\(dq\&.

+manner.  If the "charset" parameter is not set, the \fB\-\-iconv\fP option is

+refused, just as if "iconv" had been specified via "refuse options".

 .IP 

 If you wish to force users to always use \fB\-\-iconv\fP for a particular

-module, add \(dq\&no\-iconv\(dq\& to the \(dq\&refuse options\(dq\& parameter.  Keep in mind

+module, add "no\-iconv" to the "refuse options" parameter.  Keep in mind

 that this will restrict access to your module to very new rsync clients.

 .IP 

 .IP "\fBmax connections\fP"

@@ -314,15 +314,15 @@

 Any clients connecting when the maximum has been reached will receive a

 message telling them to try later.  The default is 0, which means no limit.

 A negative value disables the module.

-See also the \(dq\&lock file\(dq\& parameter.

+See also the "lock file" parameter.

 .IP 

 .IP "\fBlog file\fP"

-When the \(dq\&log file\(dq\& parameter is set to a non\-empty

+When the "log file" parameter is set to a non\-empty

 string, the rsync daemon will log messages to the indicated file rather

 than using syslog. This is particularly useful on systems (such as AIX)

 where 

 \f(CWsyslog()\fP

-doesn\(cq\&t work for chrooted programs.  The file is

+doesn't work for chrooted programs.  The file is

 opened before 

 \f(CWchroot()\fP

 is called, allowing it to be placed outside

@@ -337,7 +337,7 @@

 This setting can be overridden by using the \fB\-\-log\-file=FILE\fP or

 \fB\-\-dparam=logfile=FILE\fP command\-line options.  The former overrides

 all the log\-file parameters of the daemon and all module settings.

-The latter sets the daemon\(cq\&s log file and the default for all the

+The latter sets the daemon's log file and the default for all the

 modules, which still allows modules to override the default setting.

 .IP 

 .IP "\fBsyslog facility\fP"

 defined on your system. Common names are auth, authpriv, cron, daemon,

 ftp, kern, lpr, mail, news, security, syslog, user, uucp, local0,

 local1, local2, local3, local4, local5, local6 and local7. The default

-is daemon.  This setting has no effect if the \(dq\&log file\(dq\& setting is a

+is daemon.  This setting has no effect if the "log file" setting is a

 non\-empty string (either set in the per\-modules settings, or inherited

 from the global settings).

 .IP 

 .IP "\fBmax verbosity\fP"

 This parameter allows you to control

-the maximum amount of verbose information that you\(cq\&ll allow the daemon to

+the maximum amount of verbose information that you'll allow the daemon to

 generate (since the information goes into the log file). The default is 1,

 which allows the client to request one level of verbosity.

 .IP 

 .IP "\fBlock file\fP"

 This parameter specifies the file to use to

-support the \(dq\&max connections\(dq\& parameter. The rsync daemon uses record

+support the "max connections" parameter. The rsync daemon uses record

 locking on this file to ensure that the max connections limit is not

 exceeded for the modules sharing the lock file.

 The default is \f(CW/var/run/rsyncd.lock\fP.

 .IP 

 .IP "\fBread only\fP"

 This parameter determines whether clients

-will be able to upload files or not. If \(dq\&read only\(dq\& is true then any

-attempted uploads will fail. If \(dq\&read only\(dq\& is false then uploads will

+will be able to upload files or not. If "read only" is true then any

+attempted uploads will fail. If "read only" is false then uploads will

 be possible if file permissions on the daemon side allow them. The default

 is for all modules to be read only.

 .IP 

-Note that \(dq\&auth users\(dq\& can override this setting on a per\-user basis.

+Note that "auth users" can override this setting on a per\-user basis.

 .IP 

 .IP "\fBwrite only\fP"

 This parameter determines whether clients

-will be able to download files or not. If \(dq\&write only\(dq\& is true then any

-attempted downloads will fail. If \(dq\&write only\(dq\& is false then downloads

+will be able to download files or not. If "write only" is true then any

+attempted downloads will fail. If "write only" is false then downloads

 will be possible if file permissions on the daemon side allow them.  The

 default is for this parameter to be disabled.

 .IP 

 This parameter determines whether this module is

 listed when the client asks for a listing of available modules.  In addition,

 if this is false, the daemon will pretend the module does not exist

-when a client denied by \(dq\&hosts allow\(dq\& or \(dq\&hosts deny\(dq\& attempts to access it.

-Realize that if \(dq\&reverse lookup\(dq\& is disabled globally but enabled for the

+when a client denied by "hosts allow" or "hosts deny" attempts to access it.

+Realize that if "reverse lookup" is disabled globally but enabled for the

 module, the resulting reverse lookup to a potentially client\-controlled DNS

 server may still reveal to the client that it hit an existing module.

 The default is for modules to be listable.

 .IP "\fBuid\fP"

 This parameter specifies the user name or user ID that

 file transfers to and from that module should take place as when the daemon

-was run as root. In combination with the \(dq\&gid\(dq\& parameter this determines what

+was run as root. In combination with the "gid" parameter this determines what

 file permissions are available. The default when run by a super\-user is to

-switch to the system\(cq\&s \(dq\&nobody\(dq\& user.  The default for a non\-super\-user is to

-not try to change the user.  See also the \(dq\&gid\(dq\& parameter.

+switch to the system's "nobody" user.  The default for a non\-super\-user is to

+not try to change the user.  See also the "gid" parameter.

 .IP 

 The RSYNC_USER_NAME environment variable may be used to request that rsync run

 as the authorizing user.  For example, if you want a rsync to run as the same

 .IP "\fBgid\fP"

 This parameter specifies one or more group names/IDs that will be

 used when accessing the module.  The first one will be the default group, and

-any extra ones be set as supplemental groups.  You may also specify a \(dq\&*\(dq\& as

+any extra ones be set as supplemental groups.  You may also specify a "*" as

 the first gid in the list, which will be replaced by all the normal groups for

-the transfer\(cq\&s user (see \(dq\&uid\(dq\&).  The default when run by a super\-user is to

-switch to your OS\(cq\&s \(dq\&nobody\(dq\& (or perhaps \(dq\&nogroup\(dq\&) group with no other

+the transfer's user (see "uid").  The default when run by a super\-user is to

+switch to your OS's "nobody" (or perhaps "nogroup") group with no other

 supplementary groups.  The default for a non\-super\-user is to not change any

 group attributes (and indeed, your OS may not allow a non\-super\-user to try to

 change their group settings).

 .IP 

 .IP "\fBfake super\fP"

-Setting \(dq\&fake super = yes\(dq\& for a module causes the

+Setting "fake super = yes" for a module causes the

 daemon side to behave as if the \fB\-\-fake\-super\fP command\-line option had

 been specified.  This allows the full attributes of a file to be stored

 without having to have the daemon actually running as root.

 tampering with private administrative files, such as files you may add to

 support uid/gid name translations.

 .IP 

-The daemon filter chain is built from the \(dq\&filter\(dq\&, \(dq\&include from\(dq\&, \(dq\&include\(dq\&,

-\(dq\&exclude from\(dq\&, and \(dq\&exclude\(dq\& parameters, in that order of priority.  Anchored

+The daemon filter chain is built from the "filter", "include from", "include",

+"exclude from", and "exclude" parameters, in that order of priority.  Anchored

 patterns are anchored at the root of the module.  To prevent access to an

-entire subtree, for example, \(dq\&/secret\(dq\&, you \fImust\fP exclude everything in the

+entire subtree, for example, "/secret", you \fImust\fP exclude everything in the

 subtree; the easiest way to do this is with a triple\-star pattern like

-\(dq\&/secret/***\(dq\&.

+"/secret/***".

 .IP 

-The \(dq\&filter\(dq\& parameter takes a space\-separated list of daemon filter rules,

+The "filter" parameter takes a space\-separated list of daemon filter rules,

 though it is smart enough to know not to split a token at an internal space in

-a rule (e.g. \(dq\&\- /foo  \- /bar\(dq\& is parsed as two rules).  You may specify one or

-more merge\-file rules using the normal syntax.  Only one \(dq\&filter\(dq\& parameter can

+a rule (e.g. "\- /foo  \- /bar" is parsed as two rules).  You may specify one or

+more merge\-file rules using the normal syntax.  Only one "filter" parameter can

 apply to a given module in the config file, so put all the rules you want in a

 single parameter.  Note that per\-directory merge\-file rules do not provide as

 much protection as global rules, but they can be used to make \fB\-\-delete\fP work

 .IP "\fBexclude\fP"

 This parameter takes a space\-separated list of daemon

 exclude patterns.  As with the client \fB\-\-exclude\fP option, patterns can be

-qualified with \(dq\&\- \(dq\& or \(dq\&+ \(dq\& to explicitly indicate exclude/include.  Only one

-\(dq\&exclude\(dq\& parameter can apply to a given module.  See the \(dq\&filter\(dq\& parameter

+qualified with "\- " or "+ " to explicitly indicate exclude/include.  Only one

+"exclude" parameter can apply to a given module.  See the "filter" parameter

 for a description of how excluded files affect the daemon.

 .IP 

 .IP "\fBinclude\fP"

-Use an \(dq\&include\(dq\& to override the effects of the \(dq\&exclude\(dq\&

-parameter.  Only one \(dq\&include\(dq\& parameter can apply to a given module.  See the

-\(dq\&filter\(dq\& parameter for a description of how excluded files affect the daemon.

+Use an "include" to override the effects of the "exclude"

+parameter.  Only one "include" parameter can apply to a given module.  See the

+"filter" parameter for a description of how excluded files affect the daemon.

 .IP 

 .IP "\fBexclude from\fP"

 This parameter specifies the name of a file

 on the daemon that contains daemon exclude patterns, one per line.  Only one

-\(dq\&exclude from\(dq\& parameter can apply to a given module; if you have multiple

-exclude\-from files, you can specify them as a merge file in the \(dq\&filter\(dq\&

-parameter.  See the \(dq\&filter\(dq\& parameter for a description of how excluded files

+"exclude from" parameter can apply to a given module; if you have multiple

+exclude\-from files, you can specify them as a merge file in the "filter"

+parameter.  See the "filter" parameter for a description of how excluded files

 affect the daemon.

 .IP 

 .IP "\fBinclude from\fP"

-Analogue of \(dq\&exclude from\(dq\& for a file of daemon include

-patterns.  Only one \(dq\&include from\(dq\& parameter can apply to a given module.  See

-the \(dq\&filter\(dq\& parameter for a description of how excluded files affect the

+Analogue of "exclude from" for a file of daemon include

+patterns.  Only one "include from" parameter can apply to a given module.  See

+the "filter" parameter for a description of how excluded files affect the

 daemon.

 .IP 

 .IP "\fBincoming chmod\fP"

 this module. The usernames do not need to exist on the local

 system. The rules may contain shell wildcard characters that will be matched

 against the username provided by the client for authentication. If

-\(dq\&auth users\(dq\& is set then the client will be challenged to supply a

+"auth users" is set then the client will be challenged to supply a

 username and password to connect to the module. A challenge response

 authentication protocol is used for this exchange. The plain text

 usernames and passwords are stored in the file specified by the

-\(dq\&secrets file\(dq\& parameter. The default is for all users to be able to

-connect without a password (this is called \(dq\&anonymous rsync\(dq\&).

+"secrets file" parameter. The default is for all users to be able to

+connect without a password (this is called "anonymous rsync").

 .IP 

-In addition to username matching, you can specify groupname matching via a \(cq\&@\(cq\&

+In addition to username matching, you can specify groupname matching via a '@'

 prefix.  When using groupname matching, the authenticating username must be a

 real user on the system, or it will be assumed to be a member of no groups.

-For example, specifying \(dq\&@rsync\(dq\& will match the authenticating user if the

+For example, specifying "@rsync" will match the authenticating user if the

 named user is a member of the rsync group.

 .IP 

 Finally, options may be specified after a colon (:).  The options allow you to

-\(dq\&deny\(dq\& a user or a group, set the access to \(dq\&ro\(dq\& (read\-only), or set the access

-to \(dq\&rw\(dq\& (read/write).  Setting an auth\-rule\-specific ro/rw setting overrides

-the module\(cq\&s \(dq\&read only\(dq\& setting.

+"deny" a user or a group, set the access to "ro" (read\-only), or set the access

+to "rw" (read/write).  Setting an auth\-rule\-specific ro/rw setting overrides

+the module's "read only" setting.

 .IP 

 Be sure to put the rules in the order you want them to be matched, because the

 checking stops at the first matching user or group, and that is the only auth

 .IP 

 In the above rule, user joe will be denied access no matter what.  Any user

-that is in the group \(dq\&guest\(dq\& is also denied access.  The user \(dq\&admin\(dq\& gets

-access in read/write mode, but only if the admin user is not in group \(dq\&guest\(dq\&

+that is in the group "guest" is also denied access.  The user "admin" gets

+access in read/write mode, but only if the admin user is not in group "guest"

 (because the admin user\-matching rule would never be reached if the user is in

-group \(dq\&guest\(dq\&).  Any other user who is in group \(dq\&rsync\(dq\& will get read\-only

+group "guest").  Any other user who is in group "rsync" will get read\-only

 access.  Finally, users susan, joe, and sam get the ro/rw setting of the

-module, but only if the user didn\(cq\&t match an earlier group\-matching rule.

+module, but only if the user didn't match an earlier group\-matching rule.

 .IP 

 See the description of the secrets file for how you can have per\-user passwords

 as well as per\-group passwords.  It also explains how a user can authenticate

 using their user password or (when applicable) a group password, depending on

 what rule is being authenticated.

 .IP 

-See also the section entitled \(dq\&USING RSYNC\-DAEMON FEATURES VIA A REMOTE

-SHELL CONNECTION\(dq\& in \fBrsync\fP(1) for information on how handle an

+See also the section entitled "USING RSYNC\-DAEMON FEATURES VIA A REMOTE

+SHELL CONNECTION" in \fBrsync\fP(1) for information on how handle an

 rsyncd.conf\-level username that differs from the remote\-shell\-level

 username when using a remote shell to connect to an rsync daemon.

 .IP 

 .IP "\fBsecrets file\fP"

 This parameter specifies the name of a file that contains

 the username:password and/or @groupname:password pairs used for authenticating

-this module. This file is only consulted if the \(dq\&auth users\(dq\& parameter is

+this module. This file is only consulted if the "auth users" parameter is