Ignore:
Timestamp:
May 23, 2008, 6:56:41 AM (17 years ago)
Author:
Paul Smedley
Message:

Update source to 3.0.29

File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/samba-3.0/docs/manpages/smbd.8

    r44 r134  
    1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
    2 .de Sh \" Subsection
    3 .br
    4 .if t .Sp
    5 .ne 5
    6 .PP
    7 \fB\\$1\fR
    8 .PP
    9 ..
    10 .de Sp \" Vertical space (when we can't use .PP)
    11 .if t .sp .5v
    12 .if n .sp
    13 ..
    14 .de Ip \" List item
    15 .br
    16 .ie \\n(.$>=3 .ne \\$3
    17 .el .ne 3
    18 .IP "\\$1" \\$2
    19 ..
    20 .TH "SMBD" 8 "" "" ""
     1.\"     Title: smbd
     2.\"    Author:
     3.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
     4.\"      Date: 05/21/2008
     5.\"    Manual: System Administration tools
     6.\"    Source: Samba 3.0
     7.\"
     8.TH "SMBD" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
     9.\" disable hyphenation
     10.nh
     11.\" disable justification (adjust text to left margin only)
     12.ad l
    2113.SH "NAME"
    2214smbd - server to provide SMB/CIFS services to clients
    2315.SH "SYNOPSIS"
    2416.HP 1
    25 smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number(s)>] [-P <profiling level>] [-O <socket option>] [-s <configuration file>]
     17smbd [\-D] [\-F] [\-S] [\-i] [\-h] [\-V] [\-b] [\-d\ <debug\ level>] [\-l\ <log\ directory>] [\-p\ <port\ number(s)>] [\-P\ <profiling\ level>] [\-O\ <socket\ option>] [\-s\ <configuration\ file>]
    2618.SH "DESCRIPTION"
    2719.PP
    2820This program is part of the
    2921\fBsamba\fR(7)
    30 suite.
    31 .PP
    32 smbd
    33 is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux.
     22suite\.
     23.PP
     24smbd
     25is the server daemon that provides filesharing and printing services to Windows clients\. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol\. This is compatible with the LanManager protocol, and can service LanManager clients\. These include MSCLIENT 3\.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux\.
    3426.PP
    3527An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see
    36 \fBsmb.conf\fR(5). This man page will not describe the services, but will concentrate on the administrative aspects of running the server.
     28\fBsmb.conf\fR(5)\. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\.
    3729.PP
    3830Please note that there are significant security implications to running this server, and the
    3931\fBsmb.conf\fR(5)
    40 manual page should be regarded as mandatory reading before proceeding with installation.
    41 .PP
    42 A session is created whenever a client requests one. Each client gets a copy of the server for each session. This copy then services all connections made by the client during that session. When all connections from its client are closed, the copy of the server for that client terminates.
    43 .PP
    44 The configuration file, and any files that it includes, are automatically reloaded every minute, if they change. You can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to disconnect from the service, or
    45 smbd
    46 killed and restarted.
     32manual page should be regarded as mandatory reading before proceeding with installation\.
     33.PP
     34A session is created whenever a client requests one\. Each client gets a copy of the server for each session\. This copy then services all connections made by the client during that session\. When all connections from its client are closed, the copy of the server for that client terminates\.
     35.PP
     36The configuration file, and any files that it includes, are automatically reloaded every minute, if they change\. You can force a reload by sending a SIGHUP to the server\. Reloading the configuration file will not affect connections to any service that is already established\. Either the user will have to disconnect from the service, or
     37smbd
     38killed and restarted\.
    4739.SH "OPTIONS"
    4840.PP
    49 -D
    50 .RS 3n
    51 If specified, this parameter causes the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a daemon is the recommended way of running
    52 smbd
    53 for servers that provide more than casual use file and print services. This switch is assumed if
    54 smbd
    55 is executed on the command line of a shell.
    56 .RE
    57 .PP
    58 -F
    59 .RS 3n
     41\-D
     42.RS 4
     43If specified, this parameter causes the server to operate as a daemon\. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\. Operating the server as a daemon is the recommended way of running
     44smbd
     45for servers that provide more than casual use file and print services\. This switch is assumed if
     46smbd
     47is executed on the command line of a shell\.
     48.RE
     49.PP
     50\-F
     51.RS 4
    6052If specified, this parameter causes the main
    6153smbd
    62 process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running
     54process to not daemonize, i\.e\. double\-fork and disassociate with the terminal\. Child processes are still created as normal to service each connection request, but the main process does not exit\. This operation mode is suitable for running
    6355smbd
    6456under process supervisors such as
    … …  
    6658and
    6759svscan
    68 from Daniel J. Bernstein's
     60from Daniel J\. Bernstein\'s
    6961daemontools
    70 package, or the AIX process monitor.
    71 .RE
    72 .PP
    73 -S
    74 .RS 3n
     62package, or the AIX process monitor\.
     63.RE
     64.PP
     65\-S
     66.RS 4
    7567If specified, this parameter causes
    7668smbd
    77 to log to standard output rather than a file.
    78 .RE
    79 .PP
    80 -i
    81 .RS 3n
    82 If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell. Setting this parameter negates the implicit deamon mode when run from the command line.
     69to log to standard output rather than a file\.
     70.RE
     71.PP
     72\-i
     73.RS 4
     74If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\. Setting this parameter negates the implicit deamon mode when run from the command line\.
    8375smbd
    8476also logs to standard output, as if the
    85 -S
    86 parameter had been given.
    87 .RE
    88 .PP
    89 -V
    90 .RS 3n
    91 Prints the program version number.
    92 .RE
    93 .PP
    94 -s <configuration file>
    95 .RS 3n
    96 The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See
    97 \fIsmb.conf\fR
    98 for more information. The default configuration file name is determined at compile time.
    99 .RE
    100 .PP
    101 -d|--debuglevel=level
    102 .RS 3n
     77\-S
     78parameter had been given\.
     79.RE
     80.PP
     81\-d|\-\-debuglevel=level
     82.RS 4
    10383\fIlevel\fR
    104 is an integer from 0 to 10. The default value if this parameter is not specified is zero.
    105 .sp
    106 The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out.
    107 .sp
    108 Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.
     84is an integer from 0 to 10\. The default value if this parameter is not specified is 0\.
     85.sp
     86The higher this value, the more detail will be logged to the log files about the activities of the server\. At level 0, only critical errors and serious warnings will be logged\. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\.
     87.sp
     88Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\.
    10989.sp
    11090Note that specifying this parameter here will override the
    111 
     91\fIlog level\fR
    11292parameter in the
    113 \fIsmb.conf\fR
    114 file.
    115 .RE
    116 .PP
    117 -l|--logfile=logdirectory
    118 .RS 3n
    119 Base directory name for log/debug files. The extension
    120 \fB".progname"\fR
    121 will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client.
    122 .RE
    123 .PP
    124 -h|--help
    125 .RS 3n
    126 Print a summary of command line options.
    127 .RE
    128 .PP
    129 -b
    130 .RS 3n
    131 Prints information about how Samba was built.
    132 .RE
    133 .PP
    134 -p|--port<port number(s)>
    135 .RS 3n
     93\fIsmb\.conf\fR
     94file\.
     95.RE
     96.PP
     97\-V
     98.RS 4
     99Prints the program version number\.
     100.RE
     101.PP
     102\-s <configuration file>
     103.RS 4
     104The file specified contains the configuration details required by the server\. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\. See
     105\fIsmb\.conf\fR
     106for more information\. The default configuration file name is determined at compile time\.
     107.RE
     108.PP
     109\-l|\-\-log\-basename=logdirectory
     110.RS 4
     111Base directory name for log/debug files\. The extension
     112\fB"\.progname"\fR
     113will be appended (e\.g\. log\.smbclient, log\.smbd, etc\.\.\.)\. The log file is never removed by the client\.
     114.RE
     115.PP
     116\-h|\-\-help
     117.RS 4
     118Print a summary of command line options\.
     119.RE
     120.PP
     121\-b
     122.RS 4
     123Prints information about how Samba was built\.
     124.RE
     125.PP
     126\-p|\-\-port<port number(s)>
     127.RS 4
    136128\fIport number(s)\fR
    137 is a space or comma-separated list of TCP ports smbd should listen on. The default value is taken from the
    138 ports parameter in
    139 \fIsmb.conf\fR
    140 .sp
    141 The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP).
    142 .RE
    143 .PP
    144 -P|--profiling-level<profiling level>
    145 .RS 3n
     129is a space or comma\-separated list of TCP ports smbd should listen on\. The default value is taken from the
     130\fIports\fR
     131parameter in
     132\fIsmb\.conf\fR
     133.sp
     134The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP)\.
     135.RE
     136.PP
     137\-P|\-\-profiling\-level<profiling level>
     138.RS 4
    146139\fIprofiling level\fR
    147 is a number specifying the level of profiling data to be collected. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data.
     140is a number specifying the level of profiling data to be collected\. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data\.
    148141.RE
    149142.SH "FILES"
    150143.PP
    151 \fI/etc/inetd.conf\fR
    152 .RS 3n
     144\fI/etc/inetd\.conf\fR
     145.RS 4
    153146If the server is to be run by the
    154147inetd
    155 meta-daemon, this file must contain suitable startup information for the meta-daemon.
     148meta\-daemon, this file must contain suitable startup information for the meta\-daemon\.
    156149.RE
    157150.PP
    158151\fI/etc/rc\fR
    159 .RS 3n
    160 or whatever initialization script your system uses).
    161 .sp
    162 If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server.
     152.RS 4
     153or whatever initialization script your system uses)\.
     154.sp
     155If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\.
    163156.RE
    164157.PP
    165158\fI/etc/services\fR
    166 .RS 3n
    167 If running the server via the meta-daemon
    168 inetd, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp).
    169 .RE
    170 .PP
    171 \fI/usr/local/samba/lib/smb.conf\fR
    172 .RS 3n
     159.RS 4
     160If running the server via the meta\-daemon
     161inetd, this file must contain a mapping of service name (e\.g\., netbios\-ssn) to service port (e\.g\., 139) and protocol type (e\.g\., tcp)\.
     162.RE
     163.PP
     164\fI/usr/local/samba/lib/smb\.conf\fR
     165.RS 4
    173166This is the default location of the
    174167\fBsmb.conf\fR(5)
    175 server configuration file. Other common places that systems install this file are
    176 \fI/usr/samba/lib/smb.conf\fR
     168server configuration file\. Other common places that systems install this file are
     169\fI/usr/samba/lib/smb\.conf\fR
    177170and
    178 \fI/etc/samba/smb.conf\fR.
    179 .sp
    180 This file describes all the services the server is to make available to clients. See
     171\fI/etc/samba/smb\.conf\fR\.
     172.sp
     173This file describes all the services the server is to make available to clients\. See
    181174\fBsmb.conf\fR(5)
    182 for more information.
     175for more information\.
    183176.RE
    184177.SH "LIMITATIONS"
    … …  
    186179On some systems
    187180smbd
    188 cannot change uid back to root after a setuid() call. Such systems are called trapdoor uid systems. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or similar.
     181cannot change uid back to root after a setuid() call\. Such systems are called trapdoor uid systems\. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once\. Attempts to connect the second user will result in access denied or similar\.
    189182.SH "ENVIRONMENT VARIABLES"
    190183.PP
    191184\fBPRINTER\fR
    192 .RS 3n
     185.RS 4
    193186If no printer name is specified to printable services, most systems will use the value of this variable (or
    194187\fBlp\fR
    195 if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.
     188if this variable is not defined) as the name of the printer to use\. This is not specific to the server, however\.
    196189.RE
    197190.SH "PAM INTERACTION"
    198191.PP
    199 Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the
    200 obey pam restrictions
     192Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the
     193\fIobey pam restrictions\fR
    201194\fBsmb.conf\fR(5)
    202 paramater. When this is set, the following restrictions apply:
    203 .TP 3n
    204 \(bu
    205 \fBAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time. This also applies to encrypted logins.
    206 .TP 3n
    207 \(bu
    208 \fBSession Management\fR: When not using share level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support.
     195paramater\. When this is set, the following restrictions apply:
     196.sp
     197.RS 4
     198.ie n \{\
     199\h'-04'\(bu\h'+03'\c
     200.\}
     201.el \{\
     202.sp -1
     203.IP \(bu 2.3
     204.\}
     205\fIAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\. This also applies to encrypted logins\.
     206.RE
     207.sp
     208.RS 4
     209.ie n \{\
     210\h'-04'\(bu\h'+03'\c
     211.\}
     212.el \{\
     213.sp -1
     214.IP \(bu 2.3
     215.\}
     216\fISession Management\fR: When not using share level secuirty, users must pass PAM\'s session checks before access is granted\. Note however, that this is bypassed in share level secuirty\. Note also that some older pam configuration files may need a line added for session support\.
    209217.SH "VERSION"
    210218.PP
    211 This man page is correct for version 3.0 of the Samba suite.
     219This man page is correct for version 3\.0 of the Samba suite\.
    212220.SH "DIAGNOSTICS"
    213221.PP
    214 Most diagnostics issued by the server are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line.
    215 .PP
    216 The number and nature of diagnostics available depends on the debug level used by the server. If you have problems, set the debug level to 3 and peruse the log files.
    217 .PP
    218 Most messages are reasonably self-explanatory. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing.
     222Most diagnostics issued by the server are logged in a specified log file\. The log file name is specified at compile time, but may be overridden on the command line\.
     223.PP
     224The number and nature of diagnostics available depends on the debug level used by the server\. If you have problems, set the debug level to 3 and peruse the log files\.
     225.PP
     226Most messages are reasonably self\-explanatory\. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic\. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing\.
    219227.SH "TDB FILES"
    220228.PP
    221 Samba stores it's data in several TDB (Trivial Database) files, usually located in
    222 \fI/var/lib/samba\fR.
    223 .PP
    224 (*) information persistent across restarts (but not necessarily important to backup).
    225 .PP
    226 account_policy.tdb*
    227 .RS 3n
    228 NT account policy settings such as pw expiration, etc...
    229 .RE
    230 .PP
    231 brlock.tdb
    232 .RS 3n
     229Samba stores it\'s data in several TDB (Trivial Database) files, usually located in
     230\fI/var/lib/samba\fR\.
     231.PP
     232(*) information persistent across restarts (but not necessarily important to backup)\.
     233.PP
     234account_policy\.tdb*
     235.RS 4
     236NT account policy settings such as pw expiration, etc\.\.\.
     237.RE
     238.PP
     239brlock\.tdb
     240.RS 4
    233241byte range locks
    234242.RE
    235243.PP
    236 browse.dat
    237 .RS 3n
     244browse\.dat
     245.RS 4
    238246browse lists
    239247.RE
    240248.PP
    241 connections.tdb
    242 .RS 3n
    243 share connections (used to enforce max connections, etc...)
    244 .RE
    245 .PP
    246 gencache.tdb
    247 .RS 3n
     249connections\.tdb
     250.RS 4
     251share connections (used to enforce max connections, etc\.\.\.)
     252.RE
     253.PP
     254gencache\.tdb
     255.RS 4
    248256generic caching db
    249257.RE
    250258.PP
    251 group_mapping.tdb*
    252 .RS 3n
     259group_mapping\.tdb*
     260.RS 4
    253261group mapping information
    254262.RE
    255263.PP
    256 locking.tdb
    257 .RS 3n
     264locking\.tdb
     265.RS 4
    258266share modes & oplocks
    259267.RE
    260268.PP
    261 login_cache.tdb*
    262 .RS 3n
     269login_cache\.tdb*
     270.RS 4
    263271bad pw attempts
    264272.RE
    265273.PP
    266 messages.tdb
    267 .RS 3n
     274messages\.tdb
     275.RS 4
    268276Samba messaging system
    269277.RE
    270278.PP
    271 netsamlogon_cache.tdb*
    272 .RS 3n
     279netsamlogon_cache\.tdb*
     280.RS 4
    273281cache of user net_info_3 struct from net_samlogon() request (as a domain member)
    274282.RE
    275283.PP
    276 ntdrivers.tdb*
    277 .RS 3n
     284ntdrivers\.tdb*
     285.RS 4
    278286installed printer drivers
    279287.RE
    280288.PP
    281 ntforms.tdb*
    282 .RS 3n
     289ntforms\.tdb*
     290.RS 4
    283291installed printer forms
    284292.RE
    285293.PP
    286 ntprinters.tdb*
    287 .RS 3n
     294ntprinters\.tdb*
     295.RS 4
    288296installed printer information
    289297.RE
    290298.PP
    291299printing/
    292 .RS 3n
     300.RS 4
    293301directory containing tdb per print queue of cached lpq output
    294302.RE
    295303.PP
    296 registry.tdb
    297 .RS 3n
    298 Windows registry skeleton (connect via regedit.exe)
    299 .RE
    300 .PP
    301 sessionid.tdb
    302 .RS 3n
    303 session information (e.g. support for 'utmp = yes')
    304 .RE
    305 .PP
    306 share_info.tdb*
    307 .RS 3n
     304registry\.tdb
     305.RS 4
     306Windows registry skeleton (connect via regedit\.exe)
     307.RE
     308.PP
     309sessionid\.tdb
     310.RS 4
     311session information (e\.g\. support for \'utmp = yes\')
     312.RE
     313.PP
     314share_info\.tdb*
     315.RS 4
    308316share acls
    309317.RE
    310318.PP
    311 winbindd_cache.tdb
    312 .RS 3n
    313 winbindd's cache of user lists, etc...
    314 .RE
    315 .PP
    316 winbindd_idmap.tdb*
    317 .RS 3n
    318 winbindd's local idmap db
    319 .RE
    320 .PP
    321 wins.dat*
    322 .RS 3n
    323 wins database when 'wins support = yes'
     319winbindd_cache\.tdb
     320.RS 4
     321winbindd\'s cache of user lists, etc\.\.\.
     322.RE
     323.PP
     324winbindd_idmap\.tdb*
     325.RS 4
     326winbindd\'s local idmap db
     327.RE
     328.PP
     329wins\.dat*
     330.RS 4
     331wins database when \'wins support = yes\'
    324332.RE
    325333.SH "SIGNALS"
    … …  
    328336smbd
    329337a SIGHUP will cause it to reload its
    330 \fIsmb.conf\fR
    331 configuration file within a short period of time.
    332 .PP
    333 To shut down a user's
     338\fIsmb\.conf\fR
     339configuration file within a short period of time\.
     340.PP
     341To shut down a user\'s
    334342smbd
    335343process it is recommended that
    336 SIGKILL (-9)
    337 \fBNOT\fR
    338 be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate an
    339 smbd
    340 is to send it a SIGTERM (-15) signal and wait for it to die on its own.
     344SIGKILL (\-9)
     345\fINOT\fR
     346be used, except as a last resort, as this may leave the shared memory area in an inconsistent state\. The safe way to terminate an
     347smbd
     348is to send it a SIGTERM (\-15) signal and wait for it to die on its own\.
    341349.PP
    342350The debug log level of
    … …  
    344352may be raised or lowered using
    345353\fBsmbcontrol\fR(1)
    346 program (SIGUSR[1|2] signals are no longer used since Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level.
    347 .PP
    348 Note that as the signal handlers send a debug write, they are not re-entrant in
    349 smbd. This you should wait until
    350 smbd
    351 is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance.
     354program (SIGUSR[1|2] signals are no longer used since Samba 2\.2)\. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\.
     355.PP
     356Note that as the signal handlers send a debug write, they are not re\-entrant in
     357smbd\. This you should wait until
     358smbd
     359is in a state of waiting for an incoming SMB before issuing them\. It is possible to make the signal handlers safe by un\-blocking the signals before the select call and re\-blocking them after, however this would affect performance\.
    352360.SH "SEE ALSO"
    353361.PP
    … …  
    358366\fBsmbclient\fR(1),
    359367\fBtestparm\fR(1),
    360 \fBtestprns\fR(1), and the Internet RFC's
    361 \fIrfc1001.txt\fR,
    362 \fIrfc1002.txt\fR. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
    363 http://samba.org/cifs/.
     368\fBtestprns\fR(1), and the Internet RFC\'s
     369\fIrfc1001\.txt\fR,
     370\fIrfc1002\.txt\fR\. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
     371http://samba\.org/cifs/\.
    364372.SH "AUTHOR"
    365373.PP
    366 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.
    367 .PP
    368 The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
    369 ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
    370 
     374The 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\.
     375.PP
     376The original Samba man pages were written by Karl Auer\. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
     377ftp://ftp\.icce\.rug\.nl/pub/unix/) and updated for the Samba 2\.0 release by Jeremy Allison\. The conversion to DocBook for Samba 2\.2 was done by Gerald Carter\. The conversion to DocBook XML 4\.2 for Samba 3\.0 was done by Alexander Bokovoy\.
Note: See TracChangeset for help on using the changeset viewer.