ksmbd-tools: document duplicate key-value handling

The config parser has always ignored duplicate key-values. This may
very well be surprising to users so document it. Let's also document
how duplicate sections are handled, which conversely is typical, and
improve some wording.

Signed-off-by: Atte Heikkilä <[email protected]>
Signed-off-by: Namjae Jeon <[email protected]>

ksmbd.conf.5.in

@@ -21,11 +21,13 @@ A value may be a list of multiple values separated by commas, tabs, and spaces.
 For a list of users, all users in a system group are given by giving the group name prefixed with an at (\fB@\fR).
 A value may have a number suffix, which is either \fBK\fR, \fBM\fR, \fBG\fR, \fBT\fR, \fBP\fR, or \fBE\fR.
 A semicolon (\fB;\fR) or a hash (\fB#\fR) marks the beginning of a comment which continues until the end of the line.
+If a section has the same name as a previous section, it is a continuation of that previous section, i.e. they are the same section.
+A duplicate parameter in a section has its value updated only if its previous value was empty.
 .SH SHARES
 Each section name, except that of the \fBglobal\fR section, defines a shared resource, commonly referred to as a share.
 A section name, which is the share name, must be UTF-8, [1, 64) bytes, and is case-insensitive. \" KSMBD_REQ_MAX_SHARE_NAME
 Users that may be allowed to connect to a share are those that are present in \fBksmbdpwd.db\fR(5) user database.
-A share may limit which users are allowed to connect to a particular share.
+A share may limit which users are allowed to connect to it.
 When connected to a share, the user is mapped to a system user and underlying filesystem permissions are enforced.
 By default, this mapping is done by name, but it may also be done by mapping all users connected to the share to a single system user and group.
 When connecting as a user not in the user database, only guest sessions may work.