those produced by SMBD/CIFS clients such as Windows 95/98/ME,
Windows NT, Windows 2000, and LanManager clients. It also
participates in the browsing protocols which make up the
- Windows "Network Neighborhood" view.</para>
+ Windows "Network Neighborhood" view.</para>
<para>SMB/CIFS clients, when they start up, may wish to
locate an SMB/CIFS server. That is, they wish to know what
<para>Amongst other services, <command>nmbd</command> 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
+ 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 with the <emphasis>-n</emphasis>
option (see OPTIONS below). Thus <command>nmbd</command> will
and base filename into which operational data from
the running <command>nmbd</command> server will
be logged. The actual log file name is generated by
- appending the extension ".nmb" to the specified base
- name. For example, if the name specified was "log"
+ appending the extension ".nmb" to the specified base
+ name. For example, if the name specified was "log"
then the file log.nmb would contain the debugging data.</para>
<para>The default log file path is compiled into Samba as
and the manual pages of those components that you use. If the
manual pages aren't clear enough then please send a patch or
bug report to <ulink url="mailto:samba@samba.org">
- samba@samba.org</ulink></para>
+ samba@samba.org</ulink></para>
</para>
<para>If you have patches to submit or bugs to report
- then you may mail them directly to samba-patches@samba.org.
+ then you may mail them directly to samba-patches@samba.org.
Note, however, that due to the enormous popularity of this
package the Samba Team may take some time to respond to mail. We
prefer patches in <command>diff -u</command> format.</para>
<title>LIMITATIONS</title>
<para>On some systems <command>smbd</command> cannot change uid back
to root after a setuid() call. Such systems are called
- "trapdoor" uid systems. If you have such a system,
+ 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
+ second user will result in access denied or
similar.</para>
</refsect1>
<term>PRINTER</term>
<listitem><para>If no printer name is specified to
printable services, most systems will use the value of
- this variable (or "lp" if this variable is
+ this variable (or lp if this variable is
not defined) as the name of the printer to use. This
is not specific to the server, however.</para></listitem>
</varlistentry>
<command>inetd</command> will reread their configuration
tables if they receive a HUP signal.</para>
- <para>If your machine's name is "fred" and your
- name is "mary", you should now be able to connect
- to the service <filename>\\fred\mary</filename>.
+ <para>If your machine's name is fred and your
+ name is mary, you should now be able to connect
+ to the service <filename>\\fred\mary</filename>.
</para>
<para>To properly test and experiment with the server, we