PageRenderTime 26ms CodeModel.GetById 24ms RepoModel.GetById 0ms app.codeStats 0ms

/release/src/router/samba3/docs/htmldocs/manpages/nmbd.8.html

https://gitlab.com/envieidoc/tomato
HTML | 147 lines | 147 code | 0 blank | 0 comment | 0 complexity | bd779031bf51fb9bd04a436dc543bb99 MD5 | raw file
    

  1. <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmbd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmbd &#8212; NetBIOS name server to provide NetBIOS 
    2. 

  2. 	over IP naming services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">nmbd</code> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d &lt;debug level&gt;] [-H &lt;lmhosts file&gt;] [-l &lt;log directory&gt;] [-p &lt;port number&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><a name="id2483406"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">nmbd</code> is a server that understands 
    3. 

  3. 	and can reply to NetBIOS over IP name service requests, like 
    4. 

  4. 	those produced by SMB/CIFS clients such as Windows 95/98/ME, 
    5. 

  5. 	Windows NT, Windows 2000, Windows XP and LanManager clients. It also
    6. 

  6. 	participates in the browsing protocols which make up the 
    7. 

  7. 	Windows "Network Neighborhood" view.</p><p>SMB/CIFS clients, when they start up, may wish to 
    8. 

  8. 	locate an SMB/CIFS server. That is, they wish to know what 
    9. 

  9. 	IP number a specified host is using.</p><p>Amongst other services, <code class="literal">nmbd</code> will 
    10. 

  10. 	listen for such requests, and if its own NetBIOS name is 
    11. 

  11. 	specified it will respond with the IP number of the host it 
    12. 

  12. 	is running on.  Its "own NetBIOS name" is by
    13. 

  13. 	default the primary DNS name of the host it is running on, 
    14. 

  14. 	but this can be overridden by the <a class="link" href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a>
    15. 

  15. 	in <code class="filename">smb.conf</code>. Thus <code class="literal">nmbd</code> will 
    16. 

  16. 	reply to broadcast queries for its own name(s). Additional
    17. 

  17. 	names for <code class="literal">nmbd</code> to respond on can be set 
    18. 

  18. 	via parameters in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> configuration file.</p><p><code class="literal">nmbd</code> can also be used as a WINS 
    19. 

  19. 	(Windows Internet Name Server) server. What this basically means 
    20. 

  20. 	is that it will act as a WINS database server, creating a 
    21. 

  21. 	database from name registration requests that it receives and 
    22. 

  22. 	replying to queries from clients for these names.</p><p>In addition, <code class="literal">nmbd</code> can act as a WINS 
    23. 

  23. 	proxy, relaying broadcast queries from clients that do 
    24. 

  24. 	not understand how to talk the WINS protocol to a WINS 
    25. 

  25. 	server.</p></div><div class="refsect1" lang="en"><a name="id2483734"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes 
    26. 

  26. 		<code class="literal">nmbd</code> to operate as a daemon. That is, 
    27. 

  27. 		it detaches itself and runs in the background, fielding 
    28. 

  28. 		requests on the appropriate port. By default, <code class="literal">nmbd</code> 
    29. 

  29. 		will operate as a daemon if launched from a command shell. 
    30. 

  30. 		nmbd can also be operated from the <code class="literal">inetd</code> 
    31. 

  31. 		meta-daemon, although this is not recommended.
    32. 

  32. 		</p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
    33. 

  33. 		the main <code class="literal">nmbd</code> process to not daemonize,
    34. 

  34. 		i.e. double-fork and disassociate with the terminal.
    35. 

  35. 		Child processes are still created as normal to service
    36. 

  36. 		each connection request, but the main process does not
    37. 

  37. 		exit. This operation mode is suitable for running
    38. 

  38. 		<code class="literal">nmbd</code> under process supervisors such
    39. 

  39. 		as <code class="literal">supervise</code> and <code class="literal">svscan</code>
    40. 

  40. 		from Daniel J. Bernstein's <code class="literal">daemontools</code>
    41. 

  41. 		package, or the AIX process monitor.
    42. 

  42. 		</p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
    43. 

  43. 		<code class="literal">nmbd</code> to log to standard output rather
    44. 

  44. 		than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
    45. 

  45. 		server to run "interactively", not as a daemon, even if the
    46. 

  46. 		server is executed on the command line of a shell. Setting this
    47. 

  47. 		parameter negates the implicit daemon mode when run from the
    48. 

  48. 		command line. <code class="literal">nmbd</code> also logs to standard
    49. 

  49. 		output, as if the <code class="constant">-S</code> parameter had been
    50. 

  50. 		given. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
    51. 

  51. </p></dd><dt><span class="term">-H &lt;filename&gt;</span></dt><dd><p>NetBIOS lmhosts file.  The lmhosts 
    52. 

  52. 		file is a list of NetBIOS names to IP addresses that 
    53. 

  53. 		is loaded by the nmbd server and used via the name 
    54. 

  54. 		resolution mechanism <a class="link" href="smb.conf.5.html#NAMERESOLVEORDER" target="_top">name resolve order</a> described in <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> to resolve any 
    55. 

  55. 		NetBIOS name queries needed by the server. Note 
    56. 

  56. 		that the contents of this file are <span class="emphasis"><em>NOT</em></span> 
    57. 

  57. 		used by <code class="literal">nmbd</code> to answer any name queries. 
    58. 

  58. 		Adding a line to this file affects name NetBIOS resolution 
    59. 

  59. 		from this host <span class="emphasis"><em>ONLY</em></span>.</p><p>The default path to this file is compiled into 
    60. 

  60. 		Samba as part of the build process. Common defaults 
    61. 

  61. 		are <code class="filename">/usr/local/samba/lib/lmhosts</code>,
    62. 

  62. 		<code class="filename">/usr/samba/lib/lmhosts</code> or
    63. 

  63. 		<code class="filename">/etc/samba/lmhosts</code>. See the <a class="citerefentry" href="lmhosts.5.html"><span class="citerefentry"><span class="refentrytitle">lmhosts</span>(5)</span></a> man page for details on the contents of this file.</p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer 
    64. 

  64. from 0 to 10. The default value if this parameter is 
    65. 

  65. not specified is 0.</p><p>The higher this value, the more detail will be 
    66. 

  66. logged to the log files about the activities of the 
    67. 

  67. server. At level 0, only critical errors and serious 
    68. 

  68. warnings will be logged. Level 1 is a reasonable level for
    69. 

  69. day-to-day running - it generates a small amount of 
    70. 

  70. information about operations carried out.</p><p>Levels above 1 will generate considerable 
    71. 

  71. amounts of log data, and should only be used when 
    72. 

  72. investigating a problem. Levels above 3 are designed for 
    73. 

  73. use only by developers and generate HUGE amounts of log
    74. 

  74. data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
    75. 

  75. override the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a> parameter
    76. 

  76. in the <code class="filename">smb.conf</code> file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the program version number.
    77. 

  77. </p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the 
    78. 

  78. configuration details required by the server.  The 
    79. 

  79. information in this file includes server-specific
    80. 

  80. information such as what printcap file to use, as well 
    81. 

  81. as descriptions of all the services that the server is 
    82. 

  82. to provide. See <code class="filename">smb.conf</code> for more information.
    83. 

  83. The default configuration file name is determined at 
    84. 

  84. compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
    85. 

  85. <code class="constant">".progname"</code> will be appended (e.g. log.smbclient, 
    86. 

  86. log.smbd, etc...). The log file is never removed by the client.
    87. 

  87. </p></dd><dt><span class="term">-p &lt;UDP port number&gt;</span></dt><dd><p>UDP port number is a positive integer value.
    88. 

  88. 		This option changes the default UDP port number (normally 137)
    89. 

  89. 		that <code class="literal">nmbd</code> responds to name queries on. Don't
    90. 

  90. 		use this option unless you are an expert, in which case you
    91. 

  91. 		won't need help!</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481764"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/inetd.conf</code></span></dt><dd><p>If the server is to be run by the
    92. 

  92. 		<code class="literal">inetd</code> meta-daemon, this file
    93. 

  93. 		must contain suitable startup information for the
    94. 

  94. 		meta-daemon. 
    95. 

  95. 		</p></dd><dt><span class="term"><code class="filename">/etc/rc</code></span></dt><dd><p>or whatever initialization script your
    96. 

  96. 		system uses).</p><p>If running the server as a daemon at startup,
    97. 

  97. 		this file will need to contain an appropriate startup
    98. 

  98. 		sequence for the server.</p></dd><dt><span class="term"><code class="filename">/etc/services</code></span></dt><dd><p>If running the server via the
    99. 

  99. 		meta-daemon <code class="literal">inetd</code>, this file
    100. 

  100. 		must contain a mapping of service name (e.g., netbios-ssn)
    101. 

  101. 		to service port (e.g., 139) and protocol type (e.g., tcp).
    102. 

  102. 		</p></dd><dt><span class="term"><code class="filename">/usr/local/samba/lib/smb.conf</code></span></dt><dd><p>This is the default location of 
    103. 

  103. 		the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server
    104. 

  104. 		configuration file. Other common places that systems
    105. 

  105. 		install this file are <code class="filename">/usr/samba/lib/smb.conf</code>
    106. 

  106. 		and <code class="filename">/etc/samba/smb.conf</code>.</p><p>When run as a WINS server (see the
    107. 

  107. 			<a class="link" href="smb.conf.5.html#WINSSUPPORT" target="_top">wins support</a>
    108. 

  108. 		parameter in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> man page),
    109. 

  109. 		<code class="literal">nmbd</code>
    110. 

  110. 		will store the WINS database in the file <code class="filename">wins.dat</code>
    111. 

  111. 		in the <code class="filename">var/locks</code> directory configured under
    112. 

  112. 		wherever Samba was configured to install itself.</p><p>If <code class="literal">nmbd</code> is acting as a <span class="emphasis"><em>
    113. 

  113. 				browse master</em></span> (see the <a class="link" href="smb.conf.5.html#LOCALMASTER" target="_top">local master</a>
    114. 

  114. 		parameter in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> man page, <code class="literal">nmbd</code>
    115. 

  115. 		will store the browsing database in the file <code class="filename">browse.dat
    116. 

  116. 		</code> in the <code class="filename">var/locks</code> directory
    117. 

  117. 		configured under wherever Samba was configured to install itself.
    118. 

  118. 		</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2481969"></a><h2>SIGNALS</h2><p>To shut down an <code class="literal">nmbd</code> process it is recommended
    119. 

  119. 	that SIGKILL (-9) <span class="emphasis"><em>NOT</em></span> be used, except as a last
    120. 

  120. 	resort, as this may leave the name database in an inconsistent state.
    121. 

  121. 	The correct way to terminate <code class="literal">nmbd</code> is to send it
    122. 

  122. 	a SIGTERM (-15) signal and wait for it to die on its own.</p><p><code class="literal">nmbd</code> will accept SIGHUP, which will cause
    123. 

  123. 	it to dump out its namelists into the file <code class="filename">namelist.debug
    124. 

  124. 	</code> in the <code class="filename">/usr/local/samba/var/locks</code>
    125. 

  125. 	directory (or the <code class="filename">var/locks</code> directory configured
    126. 

  126. 	under wherever Samba was configured to install itself). This will also
    127. 

  127. 	cause <code class="literal">nmbd</code> to dump out its server database in
    128. 

  128. 	the <code class="filename">log.nmb</code> file.</p><p>The debug log level of nmbd may be raised or lowered
    129. 

  129. 	using <a class="citerefentry" href="smbcontrol.1.html"><span class="citerefentry"><span class="refentrytitle">smbcontrol</span>(1)</span></a> (SIGUSR[1|2] signals
    130. 

  130. 	are no longer used since Samba 2.2). This is to allow
    131. 

  131. 	transient problems to be diagnosed, whilst still running 
    132. 

  132. 	at a normally low log level.</p></div><div class="refsect1" lang="en"><a name="id2532519"></a><h2>VERSION</h2><p>This man page is correct for version 3.0 of 
    133. 

  133. 	the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2532530"></a><h2>SEE ALSO</h2><p>
    134. 

  134. 	<a class="citerefentry" href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a class="citerefentry" href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a class="citerefentry" href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the Internet 
    135. 

  135. 	RFC's <code class="filename">rfc1001.txt</code>, <code class="filename">rfc1002.txt</code>. 
    136. 

  136. 	In addition the CIFS (formerly SMB) specification is available 
    137. 

  137. 	as a link from the Web page <a class="ulink" href="http://samba.org/cifs/" target="_top"> 
    138. 

  138. 	http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><a name="id2532603"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 
    139. 

  139. 	were created by Andrew Tridgell. Samba is now developed
    140. 

  140. 	by the Samba Team as an Open Source project similar 
    141. 

  141. 	to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. 
    142. 

  142. 	The man page sources were converted to YODL format (another 
    143. 

  143. 	excellent piece of Open Source software, available at <a class="ulink" href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
    144. 

  144. 	ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 
    145. 

  145. 	release by Jeremy Allison.  The conversion to DocBook for 
    146. 

  146. 	Samba 2.2 was done by Gerald Carter. The conversion to DocBook
    147. 

  147. 	XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
    148. 

  148.