From: Andreas Schneider Date: Wed, 6 Oct 2021 12:01:42 +0000 (+0200) Subject: docs-xml: Remove trailing spaces in smb.conf.5.xml X-Git-Tag: ldb-2.5.0~491 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3262f69690cd3fa915fc593193a4d03194d978af;p=thirdparty%2Fsamba.git docs-xml: Remove trailing spaces in smb.conf.5.xml Signed-off-by: Andreas Schneider Reviewed-by: Ralph Boehme --- diff --git a/docs-xml/manpages/smb.conf.5.xml b/docs-xml/manpages/smb.conf.5.xml index 72664a2e457..e85c62078ac 100644 --- a/docs-xml/manpages/smb.conf.5.xml +++ b/docs-xml/manpages/smb.conf.5.xml @@ -2,7 +2,7 @@ - + smb.conf 5 @@ -83,7 +83,7 @@ - Any line beginning with a semicolon (;) or a hash (#) + Any line beginning with a semicolon (;) or a hash (#) character is ignored, as are lines containing only whitespace. @@ -117,12 +117,12 @@ A share consists of a directory to which access is being given plus a description of the access rights which are granted to the user of the service. Some housekeeping options are also specifiable. - + Sections are either file share services (used by the client as an extension of their native file systems) or printable services (used by the client to access print services on the host running the server). - + Sections may be designated guest services, in which case no password is required to access them. A specified UNIX guest account is used to define access privileges in this @@ -134,13 +134,13 @@ username. As older clients only provide passwords and not usernames, you may specify a list of usernames to check against the password using the user = option in the share definition. For modern clients such as Windows 95/98/ME/NT/2000, this should not be necessary. - + The access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system. The server does not grant more access than the host system grants. - + The following sample section defines a file space share. The user has write access to the path /home/bar. The share is accessed via the share name foo: @@ -168,19 +168,19 @@ SPECIAL SECTIONS - + The [global] section - + Parameters in this section apply to the server as a whole, or are defaults for sections that do not specifically define certain items. See the notes under PARAMETERS for more information. - + The [homes] section - + If a section called [homes] is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server. @@ -192,11 +192,11 @@ password file. If the name exists and the correct password has been given, a share is created by cloning the [homes] section. - + Some modifications are then made to the newly created share: - + The share name is changed from homes to the located username. @@ -208,7 +208,7 @@ - If you decide to use a path = line in your [homes] section, it may be useful + If you decide to use a path = line in your [homes] section, it may be useful to use the %S macro. For example: path = /data/pchome/%S @@ -217,7 +217,7 @@ - This is a fast and simple way to give a large number of clients access to their home directories with a minimum + This is a fast and simple way to give a large number of clients access to their home directories with a minimum of fuss. @@ -226,24 +226,24 @@ name is not changed to that of the requesting user. This method of using the [homes] section works well if different users share a client PC. - + - The [homes] section can specify all the parameters a normal service section can specify, though some make more sense + The [homes] section can specify all the parameters a normal service section can specify, though some make more sense than others. The following is a typical and suitable [homes] section: no - + - An important point is that if guest access is specified in the [homes] section, all home directories will be + An important point is that if guest access is specified in the [homes] section, all home directories will be visible to all clients without a password. In the very unlikely event that this is actually desirable, it is wise to also specify read only access. - The browseable flag for auto home directories will be inherited from the global browseable + The browseable flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag. This is useful as it means setting browseable = no in the [homes] section will hide the [homes] share but make any auto home directories visible. @@ -251,13 +251,13 @@ The [printers] section - + This section works like [homes], but for printers. - If a [printers] section occurs in the configuration file, users are able to connect to any printer + If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host's printcap file. @@ -283,12 +283,12 @@ - The [printers] service MUST be printable - if you specify otherwise, the server will refuse + The [printers] service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file. - + - Typically the path specified is that of a world-writeable spool directory with the sticky bit set on + Typically the path specified is that of a world-writeable spool directory with the sticky bit set on it. A typical [printers] entry looks like this: @@ -299,11 +299,11 @@ - All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. + All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file consisting of one or more lines like this: -alias|alias|alias|alias... +alias|alias|alias|alias... @@ -318,7 +318,7 @@ alias|alias|alias|alias... An alias, by the way, is defined as any component of the first entry of a printcap record. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols (|). - + On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use printcap name = lpstat to automatically obtain a list of printers. See the @@ -387,12 +387,12 @@ mkdir /usr/local/samba/lib/usershares chgrp foo /usr/local/samba/lib/usershares chmod 1770 /usr/local/samba/lib/usershares -Then add the parameters +Then add the parameters /usr/local/samba/lib/usershares 10 # (or the desired number of shares) - + to the global section of your smb.conf. Members of the group foo may then manipulate the user defined shares @@ -420,7 +420,7 @@ chmod 1770 /usr/local/samba/lib/usershares - + PARAMETERS @@ -463,7 +463,7 @@ chmod 1770 /usr/local/samba/lib/usershares session username (the username that the client wanted, not necessarily the same as the one they got). - + %G primary group name of %U. @@ -486,20 +486,20 @@ chmod 1770 /usr/local/samba/lib/usershares - + %L the NetBIOS name of the server. This allows you to change your config based on what the client calls you. Your server can have a dual personality. - + %M the Internet name of the client machine. - + %R the selected protocol level after protocol negotiation. It can be one of @@ -513,25 +513,25 @@ chmod 1770 /usr/local/samba/lib/usershares the process id of the current server process. - + %a The architecture of the remote - machine. It currently recognizes Samba (Samba), + machine. It currently recognizes Samba (Samba), the Linux CIFS file system (CIFSFS), OS/2, (OS2), - Mac OS X (OSX), Windows for Workgroups (WfWg), Windows 9x/ME + Mac OS X (OSX), Windows for Workgroups (WfWg), Windows 9x/ME (Win95), Windows NT (WinNT), Windows 2000 (Win2K), Windows XP (WinXP), Windows XP 64-bit(WinXP64), Windows 2003 including 2003R2 (Win2K3), and Windows - Vista (Vista). Anything else will be known as - UNKNOWN. + Vista (Vista). Anything else will be known as + UNKNOWN. - + %I the IP address of the client machine. @@ -576,12 +576,12 @@ chmod 1770 /usr/local/samba/lib/usershares %D name of the domain or workgroup of the current user. - + %w the winbind separator. - + %$(envvar) the value of the environment variable @@ -600,23 +600,23 @@ chmod 1770 /usr/local/samba/lib/usershares the name of the current service, if any. - + %P the root directory of the current service, if any. - + %u username of the current service, if any. - + %g primary group name of %u. - + %H the home directory of the user given by %u. @@ -627,7 +627,7 @@ chmod 1770 /usr/local/samba/lib/usershares This value is the same as %L. - + There are some quite creative things that can be done with these substitutions and other smb.conf options. @@ -636,7 +636,7 @@ chmod 1770 /usr/local/samba/lib/usershares NAME MANGLING - + Samba supports name mangling so that DOS and Windows clients can use files that don't conform to the 8.3 format. It can also be set to adjust the case of 8.3 format filenames. @@ -654,9 +654,9 @@ chmod 1770 /usr/local/samba/lib/usershares The options are: - + - + case sensitive = yes/no/auto @@ -667,7 +667,7 @@ chmod 1770 /usr/local/samba/lib/usershares DOS system supports case-sensitive filename so setting this option to auto is that same as setting it to no for them. Default auto. - + default case = upper/lower @@ -679,8 +679,8 @@ chmod 1770 /usr/local/samba/lib/usershares No are set, then the case of all incoming client filenames, not just new filenames, will be modified. See additional notes below. - - + + preserve case = yes/no @@ -688,7 +688,7 @@ chmod 1770 /usr/local/samba/lib/usershares that the client passes, or if they are forced to be the default case. Default yes. - + short preserve case = yes/no @@ -698,9 +698,9 @@ chmod 1770 /usr/local/samba/lib/usershares default case. This option can be used with preserve case = yes to permit long filenames to retain their case, while short names are lowercased. Default yes. - + - + By default, Samba 3.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving. As a special case for directories with large numbers of files, if the case @@ -708,7 +708,7 @@ chmod 1770 /usr/local/samba/lib/usershares then the "default case" option will be applied and will modify all filenames sent from the client when accessing this share. - + @@ -724,7 +724,7 @@ chmod 1770 /usr/local/samba/lib/usershares Share definitions stored in registry are used. - This is triggered by setting the global + This is triggered by setting the global parameter registry shares to yes in smb.conf. @@ -856,7 +856,7 @@ chmod 1770 /usr/local/samba/lib/usershares EXPLANATION OF EACH PARAMETER - + @@ -868,7 +868,7 @@ chmod 1770 /usr/local/samba/lib/usershares WARNINGS - + Although the configuration file permits service names to contain spaces, your client software may not. Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility. @@ -882,7 +882,7 @@ chmod 1770 /usr/local/samba/lib/usershares - Use of the [homes] and [printers] special sections make life + Use of the [homes] and [printers] special sections make life for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme care when designing these sections. In particular, ensure that the permissions on spool directories are correct. @@ -914,7 +914,7 @@ chmod 1770 /usr/local/samba/lib/usershares AUTHOR - + The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.