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/nmbd.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 "NMBD" 8 "" "" ""
     1.\"     Title: nmbd
     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 "NMBD" "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"
    2214nmbd - NetBIOS name server to provide NetBIOS over IP naming services to clients
    2315.SH "SYNOPSIS"
    2416.HP 1
    25 nmbd [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-p <port number>] [-s <configuration file>]
     17nmbd [\-D] [\-F] [\-S] [\-a] [\-i] [\-o] [\-h] [\-V] [\-d\ <debug\ level>] [\-H\ <lmhosts\ file>] [\-l\ <log\ directory>] [\-p\ <port\ number>] [\-s\ <configuration\ file>]
    2618.SH "DESCRIPTION"
    2719.PP
    2820This program is part of the
    2921\fBsamba\fR(7)
    30 suite.
    31 .PP
    32 nmbd
    33 is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view.
    34 .PP
    35 SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server. That is, they wish to know what IP number a specified host is using.
     22suite\.
     23.PP
     24nmbd
     25is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients\. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view\.
     26.PP
     27SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server\. That is, they wish to know what IP number a specified host is using\.
    3628.PP
    3729Amongst other services,
    3830nmbd
    39 will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it is running on. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this can be overridden by the
    40 netbios name in
    41 \fIsmb.conf\fR. Thus
    42 nmbd
    43 will reply to broadcast queries for its own name(s). Additional names for
     31will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it is running on\. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this can be overridden by the
     32\fInetbios name\fR
     33in
     34\fIsmb\.conf\fR\. Thus
     35nmbd
     36will reply to broadcast queries for its own name(s)\. Additional names for
    4437nmbd
    4538to respond on can be set via parameters in the
    4639\fBsmb.conf\fR(5)
    47 configuration file.
    48 .PP
    49 nmbd
    50 can also be used as a WINS (Windows Internet Name Server) server. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and replying to queries from clients for these names.
     40configuration file\.
     41.PP
     42nmbd
     43can also be used as a WINS (Windows Internet Name Server) server\. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and replying to queries from clients for these names\.
    5144.PP
    5245In addition,
    5346nmbd
    54 can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS server.
     47can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS server\.
    5548.SH "OPTIONS"
    5649.PP
    57 -D
    58 .RS 3n
     50\-D
     51.RS 4
    5952If specified, this parameter causes
    6053nmbd
    61 to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. By default,
    62 nmbd
    63 will operate as a daemon if launched from a command shell. nmbd can also be operated from the
     54to operate as a daemon\. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\. By default,
     55nmbd
     56will operate as a daemon if launched from a command shell\. nmbd can also be operated from the
    6457inetd
    65 meta-daemon, although this is not recommended.
    66 .RE
    67 .PP
    68 -F
    69 .RS 3n
     58meta\-daemon, although this is not recommended\.
     59.RE
     60.PP
     61\-F
     62.RS 4
    7063If specified, this parameter causes the main
    7164nmbd
    72 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
     65process 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
    7366nmbd
    7467under process supervisors such as
     
    7669and
    7770svscan
    78 from Daniel J. Bernstein's
     71from Daniel J\. Bernstein\'s
    7972daemontools
    80 package, or the AIX process monitor.
    81 .RE
    82 .PP
    83 -S
    84 .RS 3n
     73package, or the AIX process monitor\.
     74.RE
     75.PP
     76\-S
     77.RS 4
    8578If specified, this parameter causes
    8679nmbd
    87 to log to standard output rather than a file.
    88 .RE
    89 .PP
    90 -i
    91 .RS 3n
    92 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 daemon mode when run from the command line.
     80to log to standard output rather than a file\.
     81.RE
     82.PP
     83\-i
     84.RS 4
     85If 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 daemon mode when run from the command line\.
    9386nmbd
    9487also logs to standard output, as if the
    95 \fB-S\fR
    96 parameter had been given.
    97 .RE
    98 .PP
    99 -h|--help
    100 .RS 3n
    101 Print a summary of command line options.
    102 .RE
    103 .PP
    104 -H <filename>
    105 .RS 3n
    106 NetBIOS lmhosts file. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name resolution mechanism
    107 name resolve order described in
    108 \fBsmb.conf\fR(5)
    109 to resolve any NetBIOS name queries needed by the server. Note that the contents of this file are
    110 \fBNOT\fR
     88\fB\-S\fR
     89parameter had been given\.
     90.RE
     91.PP
     92\-h|\-\-help
     93.RS 4
     94Print a summary of command line options\.
     95.RE
     96.PP
     97\-H <filename>
     98.RS 4
     99NetBIOS lmhosts file\. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name resolution mechanism
     100\fIname resolve order\fR
     101described in
     102\fBsmb.conf\fR(5)
     103to resolve any NetBIOS name queries needed by the server\. Note that the contents of this file are
     104\fINOT\fR
    111105used by
    112106nmbd
    113 to answer any name queries. Adding a line to this file affects name NetBIOS resolution from this host
    114 \fBONLY\fR.
    115 .sp
    116 The default path to this file is compiled into Samba as part of the build process. Common defaults are
     107to answer any name queries\. Adding a line to this file affects name NetBIOS resolution from this host
     108\fIONLY\fR\.
     109.sp
     110The default path to this file is compiled into Samba as part of the build process\. Common defaults are
    117111\fI/usr/local/samba/lib/lmhosts\fR,
    118112\fI/usr/samba/lib/lmhosts\fR
    119113or
    120 \fI/etc/samba/lmhosts\fR. See the
     114\fI/etc/samba/lmhosts\fR\. See the
    121115\fBlmhosts\fR(5)
    122 man page for details on the contents of this file.
    123 .RE
    124 .PP
    125 -V
    126 .RS 3n
    127 Prints the program version number.
    128 .RE
    129 .PP
    130 -s <configuration file>
    131 .RS 3n
    132 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
    133 \fIsmb.conf\fR
    134 for more information. The default configuration file name is determined at compile time.
    135 .RE
    136 .PP
    137 -d|--debuglevel=level
    138 .RS 3n
     116man page for details on the contents of this file\.
     117.RE
     118.PP
     119\-d|\-\-debuglevel=level
     120.RS 4
    139121\fIlevel\fR
    140 is an integer from 0 to 10. The default value if this parameter is not specified is zero.
    141 .sp
    142 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.
    143 .sp
    144 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.
     122is an integer from 0 to 10\. The default value if this parameter is not specified is 0\.
     123.sp
     124The 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\.
     125.sp
     126Levels 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\.
    145127.sp
    146128Note that specifying this parameter here will override the
    147 
     129\fIlog level\fR
    148130parameter in the
    149 \fIsmb.conf\fR
    150 file.
    151 .RE
    152 .PP
    153 -l|--logfile=logdirectory
    154 .RS 3n
    155 Base directory name for log/debug files. The extension
    156 \fB".progname"\fR
    157 will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client.
    158 .RE
    159 .PP
    160 -p <UDP port number>
    161 .RS 3n
    162 UDP port number is a positive integer value. This option changes the default UDP port number (normally 137) that
    163 nmbd
    164 responds to name queries on. Don't use this option unless you are an expert, in which case you won't need help!
     131\fIsmb\.conf\fR
     132file\.
     133.RE
     134.PP
     135\-V
     136.RS 4
     137Prints the program version number\.
     138.RE
     139.PP
     140\-s <configuration file>
     141.RS 4
     142The 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
     143\fIsmb\.conf\fR
     144for more information\. The default configuration file name is determined at compile time\.
     145.RE
     146.PP
     147\-l|\-\-log\-basename=logdirectory
     148.RS 4
     149Base directory name for log/debug files\. The extension
     150\fB"\.progname"\fR
     151will be appended (e\.g\. log\.smbclient, log\.smbd, etc\.\.\.)\. The log file is never removed by the client\.
     152.RE
     153.PP
     154\-p <UDP port number>
     155.RS 4
     156UDP port number is a positive integer value\. This option changes the default UDP port number (normally 137) that
     157nmbd
     158responds to name queries on\. Don\'t use this option unless you are an expert, in which case you won\'t need help!
    165159.RE
    166160.SH "FILES"
    167161.PP
    168 \fI/etc/inetd.conf\fR
    169 .RS 3n
     162\fI/etc/inetd\.conf\fR
     163.RS 4
    170164If the server is to be run by the
    171165inetd
    172 meta-daemon, this file must contain suitable startup information for the meta-daemon.
     166meta\-daemon, this file must contain suitable startup information for the meta\-daemon\.
    173167.RE
    174168.PP
    175169\fI/etc/rc\fR
    176 .RS 3n
    177 or whatever initialization script your system uses).
    178 .sp
    179 If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server.
     170.RS 4
     171or whatever initialization script your system uses)\.
     172.sp
     173If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\.
    180174.RE
    181175.PP
    182176\fI/etc/services\fR
    183 .RS 3n
    184 If running the server via the meta-daemon
    185 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).
    186 .RE
    187 .PP
    188 \fI/usr/local/samba/lib/smb.conf\fR
    189 .RS 3n
     177.RS 4
     178If running the server via the meta\-daemon
     179inetd, 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)\.
     180.RE
     181.PP
     182\fI/usr/local/samba/lib/smb\.conf\fR
     183.RS 4
    190184This is the default location of the
    191185\fBsmb.conf\fR(5)
    192 server configuration file. Other common places that systems install this file are
    193 \fI/usr/samba/lib/smb.conf\fR
     186server configuration file\. Other common places that systems install this file are
     187\fI/usr/samba/lib/smb\.conf\fR
    194188and
    195 \fI/etc/samba/smb.conf\fR.
     189\fI/etc/samba/smb\.conf\fR\.
    196190.sp
    197191When run as a WINS server (see the
    198 wins support parameter in the
     192\fIwins support\fR
     193parameter in the
    199194\fBsmb.conf\fR(5)
    200195man page),
    201196nmbd
    202197will store the WINS database in the file
    203 \fIwins.dat\fR
     198\fIwins\.dat\fR
    204199in the
    205200\fIvar/locks\fR
    206 directory configured under wherever Samba was configured to install itself.
     201directory configured under wherever Samba was configured to install itself\.
    207202.sp
    208203If
    209204nmbd
    210205is acting as a
    211 \fB browse master\fR
     206\fI browse master\fR
    212207(see the
    213 local master parameter in the
     208\fIlocal master\fR
     209parameter in the
    214210\fBsmb.conf\fR(5)
    215211man page,
    216212nmbd
    217213will store the browsing database in the file
    218 \fIbrowse.dat \fR
     214\fIbrowse\.dat \fR
    219215in the
    220216\fIvar/locks\fR
    221 directory configured under wherever Samba was configured to install itself.
     217directory configured under wherever Samba was configured to install itself\.
    222218.RE
    223219.SH "SIGNALS"
     
    225221To shut down an
    226222nmbd
    227 process it is recommended that SIGKILL (-9)
    228 \fBNOT\fR
    229 be used, except as a last resort, as this may leave the name database in an inconsistent state. The correct way to terminate
    230 nmbd
    231 is to send it a SIGTERM (-15) signal and wait for it to die on its own.
     223process it is recommended that SIGKILL (\-9)
     224\fINOT\fR
     225be used, except as a last resort, as this may leave the name database in an inconsistent state\. The correct way to terminate
     226nmbd
     227is to send it a SIGTERM (\-15) signal and wait for it to die on its own\.
    232228.PP
    233229nmbd
    234230will accept SIGHUP, which will cause it to dump out its namelists into the file
    235 \fInamelist.debug \fR
     231\fInamelist\.debug \fR
    236232in the
    237233\fI/usr/local/samba/var/locks\fR
    238234directory (or the
    239235\fIvar/locks\fR
    240 directory configured under wherever Samba was configured to install itself). This will also cause
     236directory configured under wherever Samba was configured to install itself)\. This will also cause
    241237nmbd
    242238to dump out its server database in the
    243 \fIlog.nmb\fR
    244 file.
     239\fIlog\.nmb\fR
     240file\.
    245241.PP
    246242The debug log level of nmbd may be raised or lowered using
    247243\fBsmbcontrol\fR(1)
    248 (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.
     244(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\.
    249245.SH "VERSION"
    250246.PP
    251 This man page is correct for version 3.0 of the Samba suite.
     247This man page is correct for version 3\.0 of the Samba suite\.
    252248.SH "SEE ALSO"
    253249.PP
     
    258254\fBsmbclient\fR(1),
    259255\fBtestparm\fR(1),
    260 \fBtestprns\fR(1), and the Internet RFC's
    261 \fIrfc1001.txt\fR,
    262 \fIrfc1002.txt\fR. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
    263 http://samba.org/cifs/.
     256\fBtestprns\fR(1), and the Internet RFC\'s
     257\fIrfc1001\.txt\fR,
     258\fIrfc1002\.txt\fR\. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
     259http://samba\.org/cifs/\.
    264260.SH "AUTHOR"
    265261.PP
    266 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.
    267 .PP
    268 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
    269 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.
    270 
     262The 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\.
     263.PP
     264The 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
     265ftp://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.