diff options
Diffstat (limited to 'docs/docbook')
64 files changed, 2567 insertions, 2349 deletions
diff --git a/docs/docbook/configure b/docs/docbook/configure index 8680e5b5ab..609c17ed87 100755 --- a/docs/docbook/configure +++ b/docs/docbook/configure @@ -557,13 +557,10 @@ else echo "$ac_t""no" 1>&6 fi -if test "x$JW" = x; then - { echo "configure: error: "jw is required"" 1>&2; exit 1; } -fi # Extract the first word of "perl", so it can be a program name with args. set dummy perl; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:567: checking for $ac_word" >&5 +echo "configure:564: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_PERL'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -595,13 +592,10 @@ else echo "$ac_t""no" 1>&6 fi -if test "x$PERL" = x; then - { echo "configure: error: "perl is required"" 1>&2; exit 1; } -fi # Extract the first word of "htmldoc", so it can be a program name with args. set dummy htmldoc; ac_word=$2 echo $ac_n "checking for $ac_word""... $ac_c" 1>&6 -echo "configure:605: checking for $ac_word" >&5 +echo "configure:599: checking for $ac_word" >&5 if eval "test \"`echo '$''{'ac_cv_path_HTMLDOC'+set}'`\" = set"; then echo $ac_n "(cached) $ac_c" 1>&6 else @@ -633,9 +627,6 @@ else echo "$ac_t""no" 1>&6 fi -if test "x$HTMLDOC" = x; then - { echo "configure: error: "htmldoc is required"" 1>&2; exit 1; } -fi DOC_BUILD_DATE=`date '+%d-%m-%Y'` diff --git a/docs/docbook/configure.in b/docs/docbook/configure.in index 57482d134e..3a9ed51d16 100644 --- a/docs/docbook/configure.in +++ b/docs/docbook/configure.in @@ -1,18 +1,8 @@ AC_INIT(global.ent) -# Jade wrapper AC_PATH_PROG(JW, jw) -if test "x$JW" = x; then - AC_MSG_ERROR("jw is required") -fi AC_PATH_PROG(PERL, perl) -if test "x$PERL" = x; then - AC_MSG_ERROR("perl is required") -fi AC_PATH_PROG(HTMLDOC, htmldoc) -if test "x$HTMLDOC" = x; then - AC_MSG_ERROR("htmldoc is required") -fi DOC_BUILD_DATE=`date '+%d-%m-%Y'` AC_SUBST(DOC_BUILD_DATE) diff --git a/docs/docbook/devdoc/dev-doc.sgml b/docs/docbook/devdoc/dev-doc.sgml index b5c934b1c8..e256dbe3a2 100644 --- a/docs/docbook/devdoc/dev-doc.sgml +++ b/docs/docbook/devdoc/dev-doc.sgml @@ -12,7 +12,6 @@ <!ENTITY wins SYSTEM "wins.sgml"> <!ENTITY sam SYSTEM "sam.sgml"> <!ENTITY encryption SYSTEM "encryption.sgml"> -<!ENTITY rpc-plugin SYSTEM "rpc_plugin.sgml"> ]> <book id="Samba-Developers-Guide"> @@ -67,6 +66,5 @@ url="http://www.fsf.org/licenses/gpl.txt">http://www.fsf.org/licenses/gpl.txt</u &wins; &sam; &encryption; -&rpc-plugin; </book> diff --git a/docs/docbook/devdoc/rpc_plugin.sgml b/docs/docbook/devdoc/rpc_plugin.sgml deleted file mode 100644 index 21582a011d..0000000000 --- a/docs/docbook/devdoc/rpc_plugin.sgml +++ /dev/null @@ -1,76 +0,0 @@ -<chapter id="rpc-plugin"> -<chapterinfo> - <author> - <firstname>Anthony</firstname><surname>Liguori</surname> - <affiliation> - <orgname>IBM</orgname> - <address><email>aliguor@us.ibm.com</email></address> - </affiliation> - </author> - <pubdate>January 2003</pubdate> -</chapterinfo> - -<title>RPC Pluggable Modules</title> - -<sect1> -<title>About</title> - -<para> -This document describes how to make use the new RPC Pluggable Modules features -of Samba 3.0. This architecture was added to increase the maintainability of -Samba allowing RPC Pipes to be worked on separately from the main CVS branch. -The RPM architecture will also allow third-party vendors to add functionality -to Samba through plug-ins. -</para> - -</sect1> - -<sect1> -<title>General Overview</title> - -<para> -When an RPC call is sent to smbd, smbd tries to load a shared library by the -name <filename>librpc_<pipename>.so</filename> to handle the call if -it doesn't know how to handle the call internally. For instance, LSA calls -are handled by <filename>librpc_lsass.so</filename>.. -These shared libraries should be located in the <filename><sambaroot>/lib/rpc</filename>. smbd then attempts to call the rpc_pipe_init function within -the shared library. -</para> - -<para> -In the rpc_pipe_init function, the library should call -rpc_pipe_register_commands(). This function takes the following arguments: -</para> - -<para><programlisting> -int rpc_pipe_register_commands(const char *clnt, const char *srv, - const struct api_struct *cmds, int size); -</programlisting></para> - -<variablelist> - -<varlistentry><term>clnt</term> -<listitem><para>the Client name of the named pipe</para></listitem> -</varlistentry> - -<varlistentry><term>srv</term> -<listitem><para>the Server name of the named pipe</para></listitem> -</varlistentry> - -<varlistentry><term>cmds</term> -<listitem><para>a list of api_structs that map RPC ordinal numbers to function calls</para></listitem> -</varlistentry> - -<varlistentry><term>size</term> -<listitem><para>the number of api_structs contained in cmds</para></listitem> -</varlistentry> - -</variablelist> - -<para> -See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of -how to use this library. -</para> - -</sect1> -</chapter> diff --git a/docs/docbook/faq/clientapp.sgml b/docs/docbook/faq/clientapp.sgml index 3d44dd44c0..6d687bf772 100644 --- a/docs/docbook/faq/clientapp.sgml +++ b/docs/docbook/faq/clientapp.sgml @@ -1,8 +1,8 @@ -<chapter id="FAQ-ClientApp"> +<chapter id="ClientApp"> <title>Specific client application problems</title> <sect1> -<title>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</title> +<title>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</title> <para> When installing MS Office on a Samba drive for which you have admin user permissions, ie. admin users = username, you will find the @@ -60,16 +60,16 @@ set the following parameters on the share containing it: </para> <para><programlisting> -[MSOP95] - path = /where_you_put_it - comment = Your comment - volume = "The_CD_ROM_Label" - read only = yes - available = yes - share modes = no - locking = no - browseable = yes - public = yes + [MSOP95] + path = /where_you_put_it + comment = Your comment + volume = "The_CD_ROM_Label" + read only = yes + available = yes + share modes = no + locking = no + browseable = yes + public = yes </programlisting></para> </listitem> diff --git a/docs/docbook/faq/config.sgml b/docs/docbook/faq/config.sgml index db27102cdf..78f73252a2 100644 --- a/docs/docbook/faq/config.sgml +++ b/docs/docbook/faq/config.sgml @@ -1,4 +1,4 @@ -<chapter id="FAQ-Config"> +<chapter id="Config"> <title>Configuration problems</title> <sect1> @@ -8,18 +8,4 @@ When you have a user in 'admin users', samba will always do file operations for this user as 'root', even if 'force user' has been set. </para> </sect1> - -<sect1> -<title>I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</title> - -<para> -Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these -passwords to the unix password database, so it needs it's own user database. You can -add users to this database using "smbpasswd -a user-name". -</para> - -<para> -See also the "User database" chapter of the samba HOWTO Collection. -</para> -</sect1> </chapter> diff --git a/docs/docbook/faq/errors.sgml b/docs/docbook/faq/errors.sgml index 905e7c92c2..6476ec064e 100644 --- a/docs/docbook/faq/errors.sgml +++ b/docs/docbook/faq/errors.sgml @@ -1,4 +1,4 @@ -<chapter id="FAQ-errors"> +<chapter id="errors"> <title>Common errors</title> @@ -49,6 +49,7 @@ the samba HOWTO Collection</member> Windows NT in the chapter "Portability" of the samba HOWTO collection </member> </simplelist> +</para> </sect1> @@ -62,6 +63,7 @@ the program always prompts for the password if the server is a Samba server. It also ignores the "-N" argument when querying some (but not all) of our NT servers. </quote> +</para> <para> No, it does not ignore -N, it is just that your server rejected the diff --git a/docs/docbook/faq/features.sgml b/docs/docbook/faq/features.sgml index 66b05379cc..bc1081e5c0 100644 --- a/docs/docbook/faq/features.sgml +++ b/docs/docbook/faq/features.sgml @@ -1,4 +1,4 @@ -<chapter id="FAQ-features"> +<chapter id="features"> <title>Features</title> @@ -83,7 +83,9 @@ manual carefully.</para> <title>Tools for printing faxes</title> <para>Your incomed faxes are in: -<filename>/var/spool/fax/incoming</filename>. Print it with:</para> +<filename>/var/spool/fax/incoming</filename></para> + +<para>print it with:</para> <para><programlisting> for i in * diff --git a/docs/docbook/faq/general.sgml b/docs/docbook/faq/general.sgml index 3f7c2074f9..38bcdf49e3 100644 --- a/docs/docbook/faq/general.sgml +++ b/docs/docbook/faq/general.sgml @@ -1,4 +1,4 @@ -<chapter id="FAQ-general"> +<chapter id="general"> <title>General Information</title> <sect1> diff --git a/docs/docbook/faq/install.sgml b/docs/docbook/faq/install.sgml index f8341dc65a..88520fc71d 100644 --- a/docs/docbook/faq/install.sgml +++ b/docs/docbook/faq/install.sgml @@ -1,4 +1,4 @@ -<chapter id="FAQ-Install"> +<chapter id="Install"> <title>Compiling and installing Samba on a Unix host</title> <sect1> @@ -22,7 +22,7 @@ client to client - check your client's documentation. </sect1> <sect1> -<title>Some files that I KNOW are on the server don't show up when I view the files from my client!</title> +<title>Some files that I KNOW are on the server doesn't show up when I view the files from my client!</title> <para>See the next question.</para> </sect1> diff --git a/docs/docbook/faq/printing.sgml b/docs/docbook/faq/printing.sgml deleted file mode 100644 index cc01a5d3b0..0000000000 --- a/docs/docbook/faq/printing.sgml +++ /dev/null @@ -1,36 +0,0 @@ -<chapter id="FAQ-Printing"> -<chapterinfo> -<author> - <firstname>Ronan</firstname><surname>Waide</surname> -</author> -</chapterinfo> - -<title>Printing problems</title> - -<sect1> -<title>setdriver or cupsaddsmb failes</title> -<para> -setdriver expects the following setup: - -<simplelist> -<member>you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.</member> -<member>printer admins has to be defined in [global]</member> -<member>upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.</member> -<member>Make sure that the user you're connecting as is able to write to the print$ directories</member> -<member>Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)</member> -<member>Use setdriver to associate the driver with a printer</member> -</simplelist> - -<para> -The setdriver call will fail if the printer doesn't already exist in -samba's view of the world. Either create the printer in cups and -restart samba, or create an add printer command (see smb.conf doco) -and use RPC calls to create a printer. NB the add printer command MUST -return a single line of text indicating which port the printer was -added on. If it doesn't, Samba won't reload the printer -definitions. Although samba doesn't really support the notion of -ports, suitable add printer command and enumport command settings can -allow you pretty good remote control of the samba printer setup. -</para> -</sect1> -</chapter> diff --git a/docs/docbook/faq/sambafaq.sgml b/docs/docbook/faq/sambafaq.sgml index 2cc7d466fd..e9e5ed7a3c 100644 --- a/docs/docbook/faq/sambafaq.sgml +++ b/docs/docbook/faq/sambafaq.sgml @@ -5,7 +5,6 @@ <!ENTITY clientapp SYSTEM "clientapp.sgml"> <!ENTITY features SYSTEM "features.sgml"> <!ENTITY config SYSTEM "config.sgml"> -<!ENTITY printing SYSTEM "printing.sgml"> ]> <book id="Samba-FAQ"> @@ -35,5 +34,4 @@ and the old samba text documents which were mostly written by John Terpstra. &clientapp; &errors; &features; -&printing; </book> diff --git a/docs/docbook/manpages/findsmb.1.sgml b/docs/docbook/manpages/findsmb.1.sgml index 090b1c8388..0b3bbca017 100644 --- a/docs/docbook/manpages/findsmb.1.sgml +++ b/docs/docbook/manpages/findsmb.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="findsmb.1"> +<refentry id="findsmb"> <refmeta> <refentrytitle>findsmb</refentrytitle> @@ -23,16 +23,15 @@ <refsect1> <title>DESCRIPTION</title> - <para>This perl script is part of the <citerefentry> - <refentrytitle>Samba</refentrytitle><manvolnum>7</manvolnum></citerefentry> - suite.</para> + <para>This perl script is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>findsmb</command> is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests. - It uses <citerefentry><refentrytitle>nmblookup</refentrytitle><manvolnum>1</manvolnum></citerefentry> - and <citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum></citerefentry> - to obtain this information. + It uses <ulink url="nmblookup.1.html"><command> + nmblookup(1)</command></ulink> and <ulink url="smbclient.1.html"> + <command>smbclient(1)</command></ulink> to obtain this information. </para> </refsect1> @@ -46,17 +45,16 @@ bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. - If set, <citerefentry><refentrytitle>nmblookup</refentrytitle><manvolnum>1</manvolnum></citerefentry> + If set, <ulink url="nmblookup.1.html"><command>nmblookup</command></ulink> will be called with <constant>-B</constant> option.</para></listitem> </varlistentry> <varlistentry> <term>subnet broadcast address</term> <listitem><para>Without this option, <command>findsmb </command> will probe the subnet of the machine where - <citerefentry><refentrytitle>findsmb</refentrytitle><manvolnum>1</manvolnum></citerefentry> - is run. This value is passed to - <citerefentry><refentrytitle>nmblookup</refentrytitle><manvolnum>1</manvolnum></citerefentry> - as part of the <constant>-B</constant> option.</para></listitem> + <command>findsmb</command> is run. This value is passed + to <command>nmblookup</command> as part of the + <constant>-B</constant> option.</para></listitem> </varlistentry> </variablelist> </refsect1> @@ -78,21 +76,19 @@ version.</para> <para>The command with <constant>-r</constant> option - must be run on a system without <citerefentry> - <refentrytitle>nmbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry> running. - + must be run on a system without <ulink + url="nmbd.8.html"><command>nmbd</command></ulink> running. If <command>nmbd</command> is running on the system, you will only get the IP address and the DNS name of the machine. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root and with <constant>-r</constant> option on a machine without <command>nmbd</command> running.</para> - <para>For example, running <command>findsmb</command> - without <constant>-r</constant> option set would yield output similar + <para>For example, running <command>findsmb</command> without + <constant>-r</constant> option set would yield output similar to the following</para> -<screen> + <screen><computeroutput> IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION --------------------------------------------------------------------- 192.168.35.10 MINESET-TEST1 [DMVENGR] @@ -105,7 +101,7 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION 192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0] 192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager] 192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0] -</screen> + </computeroutput></screen> </refsect1> @@ -119,12 +115,10 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION <refsect1> <title>SEE ALSO</title> - <para><citerefentry> - <refentrytitle>nmbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry>, - <citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry>, and <citerefentry><refentrytitle>nmblookup</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> + <para><ulink url="nmbd.8.html"><command>nmbd(8)</command></ulink>, + <ulink url="smbclient.1.html"><command>smbclient(1) + </command></ulink>, and <ulink url="nmblookup.1.html"> + <command>nmblookup(1)</command></ulink> </para> </refsect1> @@ -138,11 +132,11 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION <para>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 <ulink - url="ftp://ftp.icce.rug.nl/pub/unix/">ftp://ftp.icce.rug.nl/pub/unix/</ulink>) - 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.</para> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/lmhosts.5.sgml b/docs/docbook/manpages/lmhosts.5.sgml index a8a5f2c072..7934c18e8e 100644 --- a/docs/docbook/manpages/lmhosts.5.sgml +++ b/docs/docbook/manpages/lmhosts.5.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="lmhosts.5"> +<refentry id="lmhosts"> <refmeta> <refentrytitle>lmhosts</refentrytitle> @@ -13,15 +13,15 @@ </refnamediv> <refsynopsisdiv> - <para><filename>lmhosts</filename> is the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> NetBIOS name to IP address mapping file.</para> + <para><filename>lmhosts</filename> is the <ulink url="samba.7.html"> + Samba</ulink> NetBIOS name to IP address mapping file.</para> </refsynopsisdiv> <refsect1> <title>DESCRIPTION</title> - <para>This file is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This file is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><filename>lmhosts</filename> is the <emphasis>Samba </emphasis> NetBIOS name to IP address mapping file. It @@ -35,7 +35,7 @@ <para>It is an ASCII file containing one line for NetBIOS name. The two fields on each line are separated from each other by white space. Any entry beginning with '#' is ignored. Each line - in the lmhosts file contains the following information:</para> + in the lmhosts file contains the following information :</para> <itemizedlist> <listitem><para>IP Address - in dotted decimal format.</para> @@ -52,16 +52,16 @@ </listitem> </itemizedlist> - <para>An example follows:</para> + <para>An example follows :</para> - <programlisting> + <para><programlisting> # # Sample Samba lmhosts file. # 192.9.200.1 TESTPC 192.9.200.20 NTSERVER#20 192.9.200.21 SAMBASERVER - </programlisting> + </programlisting></para> <para>Contains three IP to NetBIOS name mappings. The first and third will be returned for any queries for the names "TESTPC" @@ -73,24 +73,24 @@ be resolved.</para> <para>The default location of the <filename>lmhosts</filename> file - is in the same directory as the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file.</para> + is in the same directory as the <ulink url="smb.conf.5.html"> + smb.conf(5)></ulink> file.</para> </refsect1> <refsect1> <title>VERSION</title> - <para>This man page is correct for version 3.0 of the Samba suite.</para> + <para>This man page is correct for version 2.2 of + the Samba suite.</para> </refsect1> <refsect1> <title>SEE ALSO</title> - <para><citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry>, and <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> + <para><ulink url="smbclient.1.html"><command>smbclient(1) + </command></ulink>, <ulink url="smb.conf.5.html#NAMERESOLVEORDER"> + smb.conf(5)</ulink>, and <ulink url="smbpasswd.8.html"><command> + smbpasswd(8)</command></ulink> </para> </refsect1> @@ -108,8 +108,7 @@ <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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 was done by Alexander Bokovoy.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/net.8.sgml b/docs/docbook/manpages/net.8.sgml index 62cee8c1d7..aab9032f14 100644 --- a/docs/docbook/manpages/net.8.sgml +++ b/docs/docbook/manpages/net.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="net.8"> +<refentry id="net"> <refmeta> <refentrytitle>net</refentrytitle> @@ -42,8 +42,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>The samba net utility is meant to work just like the net utility available for windows and DOS.</para> @@ -65,8 +65,7 @@ <varlistentry> <term>-w target-workgroup</term> <listitem><para> - Sets target workgroup or domain. You have to specify - either this option or the IP address or the name of a server. + Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server. </para></listitem> </varlistentry> @@ -87,8 +86,7 @@ <varlistentry> <term>-I ip-address</term> <listitem><para> - IP address of target server to use. You have to - specify either this option or a target workgroup or a target server. + IP address of target server to use. You have to specify either this option or a target workgroup or a target server. </para></listitem> </varlistentry> @@ -116,8 +114,7 @@ <varlistentry> <term>-S server</term> <listitem><para> - Name of target server. You should specify either - this option or a target workgroup or a target IP address. + Name of target server. You should specify either this option or a target workgroup or a target IP address. </para></listitem> </varlistentry> @@ -214,7 +211,7 @@ <varlistentry> <term>SYSTEM</term> <listitem><para> - Displays the time on the remote server in a format ready for <command>/bin/date</command> + Displays the time on the remote server in a format ready for /bin/date </para></listitem> </varlistentry> @@ -222,7 +219,7 @@ <term>SET</term> <listitem><para> Tries to set the date and time of the local server to that on - the remote server using <command>/bin/date</command>. + the remote server using /bin/date. </para></listitem> </varlistentry> @@ -279,7 +276,7 @@ </varlistentry> <varlistentry> - <term>USER ADD <name> [password] [-F user flags] [misc. options]</term> + <term>USER ADD <name> [password] [-F user flags] [misc. options</term> <listitem><para> Add specified user </para></listitem> diff --git a/docs/docbook/manpages/nmbd.8.sgml b/docs/docbook/manpages/nmbd.8.sgml index 6c7ecce4e9..db920c79a1 100644 --- a/docs/docbook/manpages/nmbd.8.sgml +++ b/docs/docbook/manpages/nmbd.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="nmbd.8"> +<refentry id="nmbd"> <refmeta> <refentrytitle>nmbd</refentrytitle> @@ -35,8 +35,7 @@ <refsect1> <title>DESCRIPTION</title> - <para>This program is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This program is part of the Samba suite.</para> <para><command>nmbd</command> is a server that understands and can reply to NetBIOS over IP name service requests, like @@ -58,8 +57,8 @@ option (see OPTIONS below). Thus <command>nmbd</command> will reply to broadcast queries for its own name(s). Additional names for <command>nmbd</command> to respond on can be set - via parameters in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> configuration file.</para> + via parameters in the <ulink url="smb.conf.5.html"><filename> + smb.conf(5)</filename></ulink> configuration file.</para> <para><command>nmbd</command> can also be used as a WINS (Windows Internet Name Server) server. What this basically means @@ -125,7 +124,7 @@ server is executed on the command line of a shell. Setting this parameter negates the implicit daemon mode when run from the command line. <command>nmbd</command> also logs to standard - output, as if the <constant>-S</constant> parameter had been + output, as if the <command>-S</command> parameter had been given. </para></listitem> </varlistentry> @@ -148,10 +147,10 @@ <listitem><para>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 <ulink url="smb.conf.5.html#nameresolveorder"><parameter>name resolve - order</parameter></ulink> described in <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> to resolve any - NetBIOS name queries needed by the server. Note + resolution mechanism <ulink url="smb.conf.5.html#nameresolveorder"> + name resolve order</ulink> described in <ulink + url="smb.conf.5.html"> <filename>smb.conf(5)</filename></ulink> + to resolve any NetBIOS name queries needed by the server. Note that the contents of this file are <emphasis>NOT</emphasis> used by <command>nmbd</command> to answer any name queries. Adding a line to this file affects name NetBIOS resolution @@ -161,8 +160,9 @@ Samba as part of the build process. Common defaults are <filename>/usr/local/samba/lib/lmhosts</filename>, <filename>/usr/samba/lib/lmhosts</filename> or - <filename>/etc/samba/lmhosts</filename>. See the <citerefentry><refentrytitle>lmhosts</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> man page for details on the contents of this file.</para></listitem> + <filename>/etc/lmhosts</filename>. See the + <ulink url="lmhosts.5.html"><filename>lmhosts(5)</filename></ulink> + man page for details on the contents of this file.</para></listitem> </varlistentry> <varlistentry> @@ -191,9 +191,9 @@ cryptic.</para> <para>Note that specifying this parameter here will override - the <ulink url="smb.conf.5.html#loglevel"><parameter>log level</parameter></ulink> - parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file.</para></listitem> + the <ulink url="smb.conf.5.html#loglevel">log level</ulink> + parameter in the <ulink url="smb.conf.5.html"><filename> + smb.conf(5)</filename></ulink> file.</para></listitem> </varlistentry> <varlistentry> @@ -216,12 +216,11 @@ <term>-n <primary NetBIOS name></term> <listitem><para>This option allows you to override the NetBIOS name that Samba uses for itself. This is identical - to setting the <ulink url="smb.conf.5.html#netbiosname"><parameter>NetBIOS - name</parameter></ulink> parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. However, a command + to setting the <ulink url="smb.conf.5.html#netbiosname"> + NetBIOS name</ulink> parameter in the <ulink url="smb.conf.5.html"> + <filename>smb.conf</filename></ulink> file. However, a command line setting will take precedence over settings in - <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para></listitem> + <filename>smb.conf</filename>.</para></listitem> </varlistentry> @@ -242,8 +241,8 @@ this may be changed when Samba is autoconfigured.</para> <para>The file specified contains the configuration details - required by the server. See <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for more information. + required by the server. See <ulink url="smb.conf.5.html"> + <filename>smb.conf(5)</filename></ulink> for more information. </para></listitem> </varlistentry> </variablelist> @@ -259,7 +258,7 @@ <command>inetd</command> meta-daemon, this file must contain suitable startup information for the meta-daemon. See the <ulink - url="install.html">install</ulink> document + url="UNIX_INSTALL.html">UNIX_INSTALL.html</ulink> document for details. </para></listitem> </varlistentry> @@ -272,7 +271,7 @@ <para>If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the <ulink - url="install.html">"How to Install and Test SAMBA"</ulink> document + url="UNIX_INSTALL.html">UNIX_INSTALL.html</ulink> document for details.</para></listitem> </varlistentry> @@ -282,23 +281,21 @@ meta-daemon <command>inetd</command>, 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). - See the <ulink url="install.html">"How to Install and Test SAMBA"</ulink> + See the <ulink url="UNIX_INSTALL.html">UNIX_INSTALL.html</ulink> document for details.</para></listitem> </varlistentry> <varlistentry> <term><filename>/usr/local/samba/lib/smb.conf</filename></term> - <listitem><para>This is the default location of - the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> server - configuration file. Other common places that systems + <listitem><para>This is the default location of the + <ulink url="smb.conf.5.html"><filename>smb.conf</filename></ulink> + server configuration file. Other common places that systems install this file are <filename>/usr/samba/lib/smb.conf</filename> - and <filename>/etc/samba/smb.conf</filename>.</para> + and <filename>/etc/smb.conf</filename>.</para> <para>When run as a WINS server (see the - <ulink url="smb.conf.5.html#WINSSUPPORT"><constant>wins support</constant></ulink> - parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> man page), + <ulink url="smb.conf.5.html#WINSSUPPORT">wins support</ulink> + parameter in the <filename>smb.conf(5)</filename> man page), <command>nmbd</command> will store the WINS database in the file <filename>wins.dat</filename> in the <filename>var/locks</filename> directory configured under @@ -306,9 +303,9 @@ <para>If <command>nmbd</command> is acting as a <emphasis> browse master</emphasis> (see the <ulink - url="smb.conf.5.html#LOCALMASTER"><constant>local master</constant></ulink> - parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> man page, <command>nmbd</command> + url="smb.conf.5.html#LOCALMASTER">local master</ulink> + parameter in the <filename>smb.conf(5)</filename> man page, + <command>nmbd</command> will store the browsing database in the file <filename>browse.dat </filename> in the <filename>var/locks</filename> directory configured under wherever Samba was configured to install itself. @@ -334,11 +331,10 @@ cause <command>nmbd</command> to dump out its server database in the <filename>log.nmb</filename> file.</para> - <para>The debug log level of nmbd may be raised or lowered - using <citerefentry><refentrytitle>smbcontrol</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> (SIGUSR[1|2] signals - are no longer used since Samba 2.2). This is to allow - transient problems to be diagnosed, whilst still running + <para>The debug log level of nmbd may be raised or lowered using + <ulink url="smbcontrol.1.html"><command>smbcontrol(1)</command> + </ulink> (SIGUSR[1|2] signals are no longer used in Samba 2.2). This is + to allow transient problems to be diagnosed, whilst still running at a normally low log level.</para> </refsect1> @@ -352,15 +348,14 @@ <refsect1> <title>SEE ALSO</title> - <para> - <citerefentry><refentrytitle>inetd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, and the Internet - RFC's <filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>. + <para><command>inetd(8)</command>, <ulink + url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename> + </ulink>, <ulink url="smbclient.1.html"><command>smbclient(1) + </command></ulink>, <ulink url="testparm.1.html"><command> + testparm(1)</command></ulink>, <ulink url="testprns.1.html"> + <command>testprns(1)</command></ulink>, and the Internet RFC's + <filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>. In addition the CIFS (formerly SMB) specification is available as a link from the Web page <ulink url="http://samba.org/cifs/"> http://samba.org/cifs/</ulink>.</para> @@ -376,11 +371,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/nmblookup.1.sgml b/docs/docbook/manpages/nmblookup.1.sgml index 7dd7f105d7..33ae631ed9 100644 --- a/docs/docbook/manpages/nmblookup.1.sgml +++ b/docs/docbook/manpages/nmblookup.1.sgml @@ -36,8 +36,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>nmblookup</command> is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP @@ -66,7 +66,7 @@ query to a machine running a WINS server and the user wishes to query the names in the WINS server. If this bit is unset the normal (broadcast responding) NetBIOS processing code - on a machine is used instead. See RFC1001, RFC1002 for details. + on a machine is used instead. See rfc1001, rfc1002 for details. </para></listitem> </varlistentry> @@ -86,8 +86,8 @@ where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and - in addition, if the <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon is running on this machine it also binds to this port. + in addition, if the <ulink url="nmbd.8.html">nmbd(8)</ulink> + daemon is running on this machine it also binds to this port. </para></listitem> </varlistentry> @@ -115,8 +115,7 @@ query to the broadcast address of the network interfaces as either auto-detected or defined in the <ulink url="smb.conf.5.html#INTERFACES"><parameter>interfaces</parameter> - </ulink> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. + </ulink> parameter of the <filename>smb.conf (5)</filename> file. </para></listitem> </varlistentry> @@ -199,7 +198,7 @@ <listitem><para>This is the NetBIOS name being queried. Depending upon the previous options this may be a NetBIOS name or IP address. If a NetBIOS name then the different name types may be specified - by appending '#<type>' to the name. This name may also be + by appending '#<type>' to the name. This name may also be '*', which will return all registered names within a broadcast area.</para></listitem> </varlistentry> @@ -212,8 +211,8 @@ <para><command>nmblookup</command> can be used to query a WINS server (in the same way <command>nslookup</command> is - used to query DNS servers). To query a WINS server, <command>nmblookup</command> - must be called like this:</para> + used to query DNS servers). To query a WINS server, + <command>nmblookup</command> must be called like this:</para> <para><command>nmblookup -U server -R 'name'</command></para> @@ -234,10 +233,10 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>, and <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> + <para><ulink url="nmbd.8.html"><command>nmbd(8)</command></ulink>, + <ulink url="samba.7.html">samba(7)</ulink>, and <ulink + url="smb.conf.5.html">smb.conf(5)</ulink> + </para> </refsect1> <refsect1> @@ -250,11 +249,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/pdbedit.8.sgml b/docs/docbook/manpages/pdbedit.8.sgml index e6231bfa8c..1484bfec9a 100644 --- a/docs/docbook/manpages/pdbedit.8.sgml +++ b/docs/docbook/manpages/pdbedit.8.sgml @@ -1,7 +1,7 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY % globalentities SYSTEM '../global.ent'> %globalentities; ]> -<refentry id="pdbedit.8"> +<refentry id="pdbedit"> <refmeta> <refentrytitle>pdbedit</refentrytitle> @@ -42,8 +42,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>The pdbedit program is used to manage the users accounts stored in the sam database and can only be run by root.</para> @@ -67,11 +67,12 @@ present in the users database. This option prints a list of user/uid pairs separated by the ':' character.</para> + <para>Example: <command>pdbedit -l</command></para> - <para><screen> -sorce:500:Simo Sorce -samba:45:Test User -</screen></para> + <para><programlisting> + sorce:500:Simo Sorce + samba:45:Test User + </programlisting></para> </listitem> </varlistentry> @@ -84,26 +85,26 @@ samba:45:Test User out the account fields in a descriptive format.</para> <para>Example: <command>pdbedit -l -v</command></para> - <para><screen> ---------------- -username: sorce -user ID/Group: 500/500 -user RID/GRID: 2000/2001 -Full Name: Simo Sorce -Home Directory: \\BERSERKER\sorce -HomeDir Drive: H: -Logon Script: \\BERSERKER\netlogon\sorce.bat -Profile Path: \\BERSERKER\profile ---------------- -username: samba -user ID/Group: 45/45 -user RID/GRID: 1090/1091 -Full Name: Test User -Home Directory: \\BERSERKER\samba -HomeDir Drive: -Logon Script: -Profile Path: \\BERSERKER\profile -</screen></para> + <para><programlisting> + --------------- + username: sorce + user ID/Group: 500/500 + user RID/GRID: 2000/2001 + Full Name: Simo Sorce + Home Directory: \\BERSERKER\sorce + HomeDir Drive: H: + Logon Script: \\BERSERKER\netlogon\sorce.bat + Profile Path: \\BERSERKER\profile + --------------- + username: samba + user ID/Group: 45/45 + user RID/GRID: 1090/1091 + Full Name: Test User + Home Directory: \\BERSERKER\samba + HomeDir Drive: + Logon Script: + Profile Path: \\BERSERKER\profile + </programlisting></para> </listitem> </varlistentry> @@ -114,15 +115,14 @@ Profile Path: \\BERSERKER\profile <listitem><para>This option sets the "smbpasswd" listing format. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the - <filename>smbpasswd</filename> file format. (see the - <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for details)</para> + <filename>smbpasswd</filename> file format. (see the <ulink + url="smbpasswd.5.html"><filename>smbpasswd(5)</filename></ulink> for details)</para> <para>Example: <command>pdbedit -l -w</command></para> - <screen> -sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: -samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D: -</screen> + <para><programlisting> + sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: + samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D: + </programlisting></para> </listitem> </varlistentry> @@ -136,6 +136,8 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX operations.</para> </listitem> </varlistentry> + + <varlistentry> <term>-f fullname</term> @@ -160,6 +162,7 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX </listitem> </varlistentry> + <varlistentry> <term>-D drive</term> <listitem><para>This option can be used while adding or @@ -204,10 +207,9 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ask for the password to be used.</para> <para>Example: <command>pdbedit -a -u sorce</command> -<programlisting>new password: -retype new password -</programlisting> -</para> + <programlisting>new password: + retype new password</programlisting> + </para> </listitem> </varlistentry> @@ -279,9 +281,9 @@ retype new password maximum password age and bad lockout attempt.</para> <para>Example: <command>pdbedit -P "bad lockout attempt"</command></para> -<para><programlisting> -account policy value for bad lockout attempt is 0 -</programlisting></para> + <para><programlisting> + account policy value for bad lockout attempt is 0 + </programlisting></para> </listitem> </varlistentry> @@ -294,10 +296,10 @@ account policy value for bad lockout attempt is 0 </para> <para>Example: <command>pdbedit -P "bad lockout attempt" -V 3</command></para> -<para><programlisting> -account policy value for bad lockout attempt was 0 -account policy value for bad lockout attempt is now 3 -</programlisting></para> + <para><programlisting> + account policy value for bad lockout attempt was 0 + account policy value for bad lockout attempt is now 3 + </programlisting></para> </listitem> </varlistentry> @@ -325,9 +327,9 @@ account policy value for bad lockout attempt is now 3 <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry></para> + <para><ulink url="smbpasswd.8.html">smbpasswd(8)</ulink>, + <ulink url="samba.7.html">samba(7)</ulink> + </para> </refsect1> <refsect1> @@ -340,11 +342,11 @@ account policy value for bad lockout attempt is now 3 <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/rpcclient.1.sgml b/docs/docbook/manpages/rpcclient.1.sgml index 933938d438..10e0ff438d 100644 --- a/docs/docbook/manpages/rpcclient.1.sgml +++ b/docs/docbook/manpages/rpcclient.1.sgml @@ -1,7 +1,7 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY % globalentities SYSTEM '../global.ent'> %globalentities; ]> -<refentry id="rpcclient.1"> +<refentry id="rpcclient"> <refmeta> <refentrytitle>rpcclient</refentrytitle> @@ -36,8 +36,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>rpcclient</command> is a utility initially developed to test MS-RPC functionality in Samba itself. It has undergone @@ -56,8 +56,8 @@ <listitem><para>NetBIOS name of Server to which to connect. The server can be any SMB/CIFS server. The name is resolved using the <ulink url="smb.conf.5.html#NAMERESOLVEORDER"> - <parameter>name resolve order</parameter></ulink> line from <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para></listitem> + <parameter>name resolve order</parameter></ulink> line from + <filename>smb.conf(5)</filename>.</para></listitem> </varlistentry> @@ -68,11 +68,11 @@ password used in the connection. The format of the file is </para> -<para><programlisting> -username = <value> -password = <value> -domain = <value> -</programlisting></para> + <para><programlisting> + username = <value> + password = <value> + domain = <value> + </programlisting></para> <para>Make certain that the permissions on the file restrict access from unwanted users. </para></listitem> @@ -85,10 +85,13 @@ domain = <value> <listitem><para>execute semicolon separated commands (listed below)) </para></listitem> </varlistentry> + + + - &stdarg.help; &stdarg.debuglevel; - + &stdarg.help; + <varlistentry> <term>-I IP-address</term> <listitem><para><replaceable>IP address</replaceable> is the address of the server to connect to. @@ -160,6 +163,9 @@ domain = <value> it in directly. </para></listitem> </varlistentry> + + + <varlistentry> <term>-W|--workgroup=domain</term> <listitem><para>Set the SMB domain of the username. This @@ -169,6 +175,7 @@ domain = <value> opposed to the Domain SAM). </para></listitem> </varlistentry> + </variablelist> </refsect1> @@ -207,10 +214,12 @@ domain = <value> </itemizedlist> <para> </para> + + <para><emphasis>SPOOLSS</emphasis></para> <itemizedlist> - <listitem><para><command>adddriver <arch> <config></command> + <listitem><para><command>adddriver <arch> <config></command> - Execute an AddPrinterDriver() RPC to install the printer driver information on the server. Note that the driver files should already exist in the directory returned by @@ -220,16 +229,16 @@ domain = <value> The <parameter>config</parameter> parameter is defined as follows: </para> -<para><programlisting> -Long Printer Name:\ -Driver File Name:\ -Data File Name:\ -Config File Name:\ -Help File Name:\ -Language Monitor Name:\ -Default Data Type:\ -Comma Separated list of Files -</programlisting></para> + <para><programlisting> + Long Printer Name:\ + Driver File Name:\ + Data File Name:\ + Config File Name:\ + Help File Name:\ + Language Monitor Name:\ + Default Data Type:\ + Comma Separated list of Files + </programlisting></para> <para>Any empty fields should be enter as the string "NULL". </para> @@ -239,7 +248,10 @@ Comma Separated list of Files be "NULL". On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail. </para></listitem> - + + + + <listitem><para><command>addprinter <printername> <sharename> <drivername> <port></command> - Add a printer on the remote server. This printer @@ -375,7 +387,7 @@ Comma Separated list of Files <para>From Luke Leighton's original rpcclient man page:</para> - <para><emphasis>WARNING!</emphasis> The MSRPC over SMB code has + <para><emphasis>"WARNING!</emphasis> The MSRPC over SMB code has been developed from examining Network traces. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work. Microsoft's @@ -383,13 +395,12 @@ Comma Separated list of Files to be... a bit flaky in places. </para> <para>The development of Samba's implementation is also a bit rough, - and as more of the services are understood, it can even result in - versions of <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rpcclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> that are incompatible for some commands or services. Additionally, + and as more of the services are understood, it can even result in + versions of <command>smbd(8)</command> and <command>rpcclient(1)</command> + that are incompatible for some commands or services. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may - result in incompatibilities.</para> + result in incompatibilities." </para> </refsect1> @@ -411,8 +422,7 @@ Comma Separated list of Files <para>The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. 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.</para> + Carter.</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/samba.7.sgml b/docs/docbook/manpages/samba.7.sgml index a352a6a7c6..17865edd81 100644 --- a/docs/docbook/manpages/samba.7.sgml +++ b/docs/docbook/manpages/samba.7.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="samba.7"> +<refentry id="samba"> <refmeta> <refentrytitle>samba</refentrytitle> @@ -8,7 +8,7 @@ <refnamediv> - <refname>Samba</refname> + <refname>SAMBA</refname> <refpurpose>A Windows SMB/CIFS fileserver for UNIX</refpurpose> </refnamediv> @@ -29,30 +29,26 @@ <variablelist> <varlistentry> - <term><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command>smbd</command> daemon provides the file and print services to + <term><command>smbd</command></term> + <listitem><para>The <command>smbd </command> + daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file - for this daemon is described in <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> + for this daemon is described in <filename>smb.conf</filename> </para></listitem> </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> + <term><command>nmbd</command></term> <listitem><para>The <command>nmbd</command> daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon - is described in <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></para> + is described in <filename>smb.conf</filename></para> </listitem> </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> + <term><command>smbclient</command></term> <listitem><para>The <command>smbclient</command> program implements a simple ftp-like client. This is useful for accessing SMB shares on other compatible @@ -63,17 +59,15 @@ </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> + <term><command>testparm</command></term> <listitem><para>The <command>testparm</command> - utility is a simple syntax checker for Samba's <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> configuration file.</para> + utility is a simple syntax checker for Samba's + <filename>smb.conf</filename>configuration file.</para> </listitem> </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> + <term><command>testprns</command></term> <listitem><para>The <command>testprns</command> utility supports testing printer names defined in your <filename>printcap</filename> file used @@ -82,8 +76,7 @@ </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>smbstatus</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> + <term><command>smbstatus</command></term> <listitem><para>The <command>smbstatus</command> tool provides access to information about the current connections to <command>smbd</command>.</para> @@ -91,8 +84,7 @@ </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>nmblookup</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> + <term><command>nmblookup</command></term> <listitem><para>The <command>nmblookup</command> tools allows NetBIOS name queries to be made from a UNIX host.</para> @@ -100,18 +92,15 @@ </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>smbgroupedit</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command>smbgroupedit</command> - tool allows for mapping unix groups to NT Builtin, - Domain, or Local groups. Also it allows setting - priviledges for that group, such as saAddUser, etc.</para> + <term><command>make_smbcodepage</command></term> + <listitem><para>The <command>make_smbcodepage</command> + utility provides a means of creating SMB code page + definition files for your <command>smbd</command> server.</para> </listitem> </varlistentry> <varlistentry> - <term><citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> + <term><command>smbpasswd</command></term> <listitem><para>The <command>smbpasswd</command> command is a tool for changing LanMan and Windows NT password hashes on Samba and Windows NT servers.</para> @@ -158,8 +147,8 @@ list. Details on how to join the mailing list are given in the README file that comes with Samba.</para> - <para>If you have access to a WWW viewer (such as Mozilla - or Konqueror) then you will also find lots of useful information, + <para>If you have access to a WWW viewer (such as Netscape + or Mosaic) then you will also find lots of useful information, including back issues of the Samba mailing list, at <ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>.</para> </refsect1> @@ -167,7 +156,7 @@ <refsect1> <title>VERSION</title> - <para>This man page is correct for version 3.0 of the + <para>This man page is correct for version 2.2 of the Samba suite. </para> </refsect1> @@ -181,8 +170,8 @@ <para>If you have patches to submit, visit <ulink url="http://devel.samba.org/">http://devel.samba.org/</ulink> - for information on how to do it properly. We prefer patches - in <command>diff -u</command> format.</para> + for information on how to do it properly. We prefer patches in + <command>diff -u</command> format.</para> </refsect1> <refsect1> @@ -217,11 +206,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smb.conf.5.sgml b/docs/docbook/manpages/smb.conf.5.sgml index 7aaa189578..08a23a22bd 100644 --- a/docs/docbook/manpages/smb.conf.5.sgml +++ b/docs/docbook/manpages/smb.conf.5.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smb.conf.5"> +<refentry id="smb.conf"> <refmeta> <refentrytitle>smb.conf</refentrytitle> @@ -15,13 +15,14 @@ <refsect1> <title>SYNOPSIS</title> - <para>The <filename>smb.conf</filename> file is a configuration - file for the Samba suite. <filename>smb.conf</filename> contains - runtime configuration information for the Samba programs. The <filename>smb.conf</filename> file - is designed to be configured and administered by the <citerefentry><refentrytitle>swat</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> program. The complete - description of the file format and possible parameters held within - are here for reference purposes.</para> </refsect1> + <para>The <filename>smb.conf</filename> file is a configuration + file for the Samba suite. <filename>smb.conf</filename> contains + runtime configuration information for the Samba programs. The + <filename>smb.conf</filename> file is designed to be configured and + administered by the <ulink url="swat.8.html"><command>swat(8)</command> + </ulink> program. The complete description of the file format and + possible parameters held within are here for reference purposes.</para> +</refsect1> <refsect1> <title id="FILEFORMATSECT">FILE FORMAT</title> @@ -104,13 +105,13 @@ The user has write access to the path <filename>/home/bar</filename>. The share is accessed via the share name "foo":</para> -<screen> -<computeroutput> -[foo] - path = /home/bar - read only = no -</computeroutput> -</screen> + <screen> + <computeroutput> + [foo] + path = /home/bar + read only = no + </computeroutput> + </screen> <para>The following sample section defines a printable share. The share is readonly, but printable. That is, the only write @@ -119,15 +120,15 @@ access will be permitted as the default guest user (specified elsewhere):</para> -<screen> -<computeroutput> -[aprinter] - path = /usr/spool/public - read only = yes - printable = yes - guest ok = yes -</computeroutput> -</screen> + <screen> + <computeroutput> + [aprinter] + path = /usr/spool/public + read only = yes + printable = yes + guest ok = yes + </computeroutput> + </screen> </refsect1> <refsect1> @@ -191,12 +192,12 @@ than others. The following is a typical and suitable [homes] section:</para> -<screen> -<computeroutput> -[homes] - read only = no -</computeroutput> -</screen> + <screen> + <computeroutput> + [homes] + read only = no + </computeroutput> + </screen> <para>An important point is that if guest access is specified in the [homes] section, all home directories will be @@ -256,12 +257,12 @@ it. A typical [printers] entry would look like this:</para> -<screen><computeroutput> -[printers] - path = /usr/spool/public - guest ok = yes - printable = yes -</computeroutput></screen> + <screen><computeroutput> + [printers] + path = /usr/spool/public + guest ok = yes + printable = yes + </computeroutput></screen> <para>All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. @@ -269,11 +270,11 @@ to set up a pseudo-printcap. This is a file consisting of one or more lines like this:</para> -<screen> -<computeroutput> -alias|alias|alias|alias... -</computeroutput> -</screen> + <screen> + <computeroutput> + alias|alias|alias|alias... + </computeroutput> + </screen> <para>Each alias should be an acceptable printer name for your printing subsystem. In the [global] section, specify @@ -471,7 +472,7 @@ alias|alias|alias|alias... </variablelist> <para>There are some quite creative things that can be done - with these substitutions and other smb.conf options.</para> + with these substitutions and other smb.conf options.</para </refsect1> <refsect1> @@ -551,7 +552,7 @@ alias|alias|alias|alias... then steps 1 to 5 are skipped.</para> - <orderedlist numeration="arabic"> + <orderedlist numeration="Arabic"> <listitem><para>If the client has passed a username/password pair and that username/password pair is validated by the UNIX system's password programs then the connection is made as that @@ -684,7 +685,6 @@ alias|alias|alias|alias... <listitem><para><link linkend="LOGONSCRIPT"><parameter>logon script</parameter></link></para></listitem> <listitem><para><link linkend="LPQCACHETIME"><parameter>lpq cache time</parameter></link></para></listitem> <listitem><para><link linkend="MACHINEPASSWORDTIMEOUT"><parameter>machine password timeout</parameter></link></para></listitem> - <listitem><para><link linkend="MANGLEPREFIX"><parameter>mangle prefix</parameter></link></para></listitem> <listitem><para><link linkend="MANGLEDSTACK"><parameter>mangled stack</parameter></link></para></listitem> <listitem><para><link linkend="MAPTOGUEST"><parameter>map to guest</parameter></link></para></listitem> <listitem><para><link linkend="MAXDISKSIZE"><parameter>max disk size</parameter></link></para></listitem> @@ -730,6 +730,7 @@ alias|alias|alias|alias... <listitem><para><link linkend="PRELOAD"><parameter>preload</parameter></link></para></listitem> <listitem><para><link linkend="PRINTCAP"><parameter>printcap</parameter></link></para></listitem> <listitem><para><link linkend="PRINTCAPNAME"><parameter>printcap name</parameter></link></para></listitem> + <listitem><para><link linkend="PRINTERDRIVERFILE"><parameter>printer driver file</parameter></link></para></listitem> <listitem><para><link linkend="PRIVATEDIR"><parameter>private dir</parameter></link></para></listitem> <listitem><para><link linkend="PROTOCOL"><parameter>protocol</parameter></link></para></listitem> <listitem><para><link linkend="READBMPX"><parameter>read bmpx</parameter></link></para></listitem> @@ -769,6 +770,7 @@ alias|alias|alias|alias... <listitem><para><link linkend="UNIXPASSWORDSYNC"><parameter>unix password sync</parameter></link></para></listitem> <listitem><para><link linkend="UPDATEENCRYPTED"><parameter>update encrypted</parameter></link></para></listitem> <listitem><para><link linkend="USEMMAP"><parameter>use mmap</parameter></link></para></listitem> + <listitem><para><link linkend="USERHOSTS"><parameter>use rhosts</parameter></link></para></listitem> <listitem><para><link linkend="USESENDFILE"><parameter>use sendfile</parameter></link></para></listitem> <listitem><para><link linkend="USERNAMELEVEL"><parameter>username level</parameter></link></para></listitem> <listitem><para><link linkend="USERNAMEMAP"><parameter>username map</parameter></link></para></listitem> @@ -804,7 +806,7 @@ alias|alias|alias|alias... <listitem><para><link linkend="ALLOWHOSTS"><parameter>allow hosts</parameter></link></para></listitem> <listitem><para><link linkend="AVAILABLE"><parameter>available</parameter></link></para></listitem> <listitem><para><link linkend="BLOCKINGLOCKS"><parameter>blocking locks</parameter></link></para></listitem> - <listitem><para><link linkend="BLOCKSIZE"><parameter>block size</parameter></link></para></listitem> +<listitem><para><link linkend="BLOCKSIZE"><parameter>block size</parameter></link></para></listitem> <listitem><para><link linkend="BROWSABLE"><parameter>browsable</parameter></link></para></listitem> <listitem><para><link linkend="BROWSEABLE"><parameter>browseable</parameter></link></para></listitem> <listitem><para><link linkend="CASESENSITIVE"><parameter>case sensitive</parameter></link></para></listitem> @@ -880,6 +882,7 @@ alias|alias|alias|alias... <listitem><para><link linkend="PATH"><parameter>path</parameter></link></para></listitem> <listitem><para><link linkend="POSIXLOCKING"><parameter>posix locking</parameter></link></para></listitem> <listitem><para><link linkend="POSTEXEC"><parameter>postexec</parameter></link></para></listitem> + <listitem><para><link linkend="POSTSCRIPT"><parameter>postscript</parameter></link></para></listitem> <listitem><para><link linkend="PREEXEC"><parameter>preexec</parameter></link></para></listitem> <listitem><para><link linkend="PREEXECCLOSE"><parameter>preexec close</parameter></link></para></listitem> <listitem><para><link linkend="PRESERVECASE"><parameter>preserve case</parameter></link></para></listitem> @@ -888,6 +891,8 @@ alias|alias|alias|alias... <listitem><para><link linkend="PRINTABLE"><parameter>printable</parameter></link></para></listitem> <listitem><para><link linkend="PRINTER"><parameter>printer</parameter></link></para></listitem> <listitem><para><link linkend="PRINTERADMIN"><parameter>printer admin</parameter></link></para></listitem> + <listitem><para><link linkend="PRINTERDRIVER"><parameter>printer driver</parameter></link></para></listitem> + <listitem><para><link linkend="PRINTERDRIVERLOCATION"><parameter>printer driver location</parameter></link></para></listitem> <listitem><para><link linkend="PRINTERNAME"><parameter>printer name</parameter></link></para></listitem> <listitem><para><link linkend="PRINTING"><parameter>printing</parameter></link></para></listitem> <listitem><para><link linkend="PUBLIC"><parameter>public</parameter></link></para></listitem> @@ -933,10 +938,10 @@ alias|alias|alias|alias... <variablelist> <varlistentry> - <term><anchor id="ABORTSHUTDOWNSCRIPT"/>abort shutdown script (G)</term> + <term><anchor id="ABORTSHUTDOWNSCRIPT">abort shutdown script (G)</term> <listitem><para><emphasis>This parameter only exists in the HEAD cvs branch</emphasis> - This a full path name to a script called by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> that + This a full path name to a script called by + <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> that should stop a shutdown procedure issued by the <link linkend="SHUTDOWNSCRIPT"><parameter>shutdown script</parameter></link>.</para> @@ -948,7 +953,7 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ADDPRINTERCOMMAND"/>addprinter command (G)</term> + <term><anchor id="ADDPRINTERCOMMAND">addprinter command (G)</term> <listitem><para>With the introduction of MS-RPC based printing support for Windows NT/2000 clients in Samba 2.2, The MS Add Printer Wizard (APW) icon is now also available in the @@ -962,12 +967,12 @@ alias|alias|alias|alias... will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the <filename>smb.conf</filename> file in order that it can be - shared by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>.</para> + shared by <ulink url="smbd.8.html"><command>smbd(8)</command> + </ulink>.</para> <para>The <parameter>addprinter command</parameter> is automatically invoked with the following parameter (in - order):</para> + order:</para> <itemizedlist> <listitem><para><parameter>printer name</parameter></para></listitem> @@ -984,22 +989,16 @@ alias|alias|alias|alias... driver location" parameter is included for backwards compatibility only. The remaining fields in the structure are generated from answers to the APW questions.</para> - + <para>Once the <parameter>addprinter command</parameter> has been executed, <command>smbd</command> will reparse the <filename> smb.conf</filename> to determine if the share defined by the APW exists. If the sharename is still invalid, then <command>smbd </command> will return an ACCESS_DENIED error to the client.</para> - - <para> - The "add printer command" program can output a single line of text, - which Samba will set as the port the new printer is connected to. - If this line isn't output, Samba won't reload its printer shares. - </para> <para>See also <link linkend="DELETEPRINTERCOMMAND"><parameter> deleteprinter command</parameter></link>, <link - linkend="PRINTING"><parameter>printing</parameter></link>, + linkend="printing"><parameter>printing</parameter></link>, <link linkend="SHOWADDPRINTERWIZARD"><parameter>show add printer wizard</parameter></link></para> @@ -1012,7 +1011,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="ADDSHARECOMMAND"/>add share command (G)</term> + <term><anchor id="ADDSHARECOMMAND">add share command (G)</term> <listitem><para>Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The <parameter>add share command</parameter> is used to define an @@ -1066,10 +1065,9 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="ADDMACHINESCRIPT"/>add machine script (G)</term> + <term><anchor id="ADDMACHINESCRIPT">add machine script (G)</term> <listitem><para>This is the full pathname to a script that will - be run by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when a machine is added + be run by <ulink url="smbd.8.html">smbd(8)</ulink> when a machine is added to it's domain using the administrator username and password method. </para> <para>This option is only required when using sam back-ends tied to the @@ -1085,7 +1083,7 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ADSSERVER"/>ads server (G)</term> + <term><anchor id="ADSSERVER">ads server (G)</term> <listitem><para>If this option is specified, samba does not try to figure out what ads server to use itself, but uses the specified ads server. Either one DNS name or IP @@ -1098,10 +1096,10 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ADDUSERSCRIPT"/>add user script (G)</term> + <term><anchor id="ADDUSERSCRIPT">add user script (G)</term> <listitem><para>This is the full pathname to a script that will - be run <emphasis>AS ROOT</emphasis> by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> under special circumstances described below.</para> + be run <emphasis>AS ROOT</emphasis> by <ulink url="smbd.8.html">smbd(8) + </ulink> under special circumstances described below.</para> <para>Normally, a Samba server requires that UNIX users are created for all users accessing files on this server. For sites @@ -1111,16 +1109,16 @@ alias|alias|alias|alias... url="smbd.8.html">smbd</ulink> to create the required UNIX users <emphasis>ON DEMAND</emphasis> when a user accesses the Samba server.</para> - <para>In order to use this option, <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> must <emphasis>NOT</emphasis> be set to <parameter>security = share</parameter> + <para>In order to use this option, <ulink url="smbd.8.html">smbd</ulink> + must <emphasis>NOT</emphasis> be set to <parameter>security = share</parameter> and <parameter>add user script</parameter> must be set to a full pathname for a script that will create a UNIX user given one argument of <parameter>%u</parameter>, which expands into the UNIX user name to create.</para> <para>When the Windows user attempts to access the Samba server, - at login (session setup in the SMB protocol) time, <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> contacts the <parameter>password server</parameter> and + at login (session setup in the SMB protocol) time, <ulink url="smbd.8.html"> + smbd</ulink> contacts the <parameter>password server</parameter> and attempts to authenticate the given user with the given password. If the authentication succeeds then <command>smbd</command> attempts to find a UNIX user in the UNIX password database to map the @@ -1148,10 +1146,10 @@ alias|alias|alias|alias... </listitem> </varlistentry> - <varlistentry><term><anchor id="ADDGROUPSCRIPT"/>add group script (G)</term> + <varlistentry><term><anchor id="ADDGROUPSCRIPT">add group script (G)</term> <listitem><para>This is the full pathname to a script that will - be run <emphasis>AS ROOT</emphasis> by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when a new group is + be run <emphasis>AS ROOT</emphasis> by <ulink + url="smbd.8.html">smbd(8)</ulink> when a new group is requested. It will expand any <parameter>%g</parameter> to the group name passed. This script is only useful for installations using the @@ -1164,7 +1162,7 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ADMINUSERS"/>admin users (S)</term> + <term><anchor id="ADMINUSERS">admin users (S)</term> <listitem><para>This is a list of users who will be granted administrative privileges on the share. This means that they will do all file operations as the super-user (root).</para> @@ -1180,13 +1178,13 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ADDUSERTOGROUPSCRIPT"/>add user to group script (G)</term> + <term><anchor id="ADDUSERTOGROUPSCRIPT">add user to group script (G)</term> <listitem><para>Full path to the script that will be called when a user is added to a group using the Windows NT domain administration - tools. It will be run by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> <emphasis>AS ROOT</emphasis>. - Any <parameter>%g</parameter> will be replaced with the group name and - any <parameter>%u</parameter> will be replaced with the user name. + tools. It will be run by <ulink url="smbd.8.html">smbd(8)</ulink> + <emphasis>AS ROOT</emphasis>. Any <parameter>%g</parameter> will be + replaced with the group name and any <parameter>%u</parameter> will + be replaced with the user name. </para> <para>Default: <command>add user to group script = </command></para> @@ -1197,13 +1195,13 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ALLOWHOSTS"/>allow hosts (S)</term> + <term><anchor id="ALLOWHOSTS">allow hosts (S)</term> <listitem><para>Synonym for <link linkend="HOSTSALLOW"> <parameter>hosts allow</parameter></link>.</para></listitem> </varlistentry> <varlistentry> - <term><anchor id="ALGORITHMICRIDBASE"/>algorithmic rid base (G)</term> + <term><anchor id="ALGORITHMICRIDBASE">algorithmic rid base (G)</term> <listitem><para>This determines how Samba will use its algorithmic mapping from uids/gid to the RIDs needed to construct NT Security Identifiers.</para> @@ -1226,7 +1224,7 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ALLOWTRUSTEDDOMAINS"/>allow trusted domains (G)</term> + <term><anchor id="ALLOWTRUSTEDDOMAINS">allow trusted domains (G)</term> <listitem><para>This option only takes effect when the <link linkend="SECURITY"><parameter>security</parameter></link> option is set to <constant>server</constant> or <constant>domain</constant>. @@ -1250,9 +1248,10 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="ANNOUNCEAS"/>announce as (G)</term> - <listitem><para>This specifies what type of server <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will announce itself as, to a network neighborhood browse + <term><anchor id="ANNOUNCEAS">announce as (G)</term> + <listitem><para>This specifies what type of server + <ulink url="nmbd.8.html"><command>nmbd</command></ulink> + will announce itself as, to a network neighborhood browse list. By default this is set to Windows NT. The valid options are : "NT Server" (which can also be written as "NT"), "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, @@ -1271,7 +1270,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="ANNOUNCEVERSION"/>announce version (G)</term> + <term><anchor id="ANNOUNCEVERSION">announce version (G)</term> <listitem><para>This specifies the major and minor version numbers that nmbd will use when announcing itself as a server. The default is 4.9. Do not change this parameter unless you have a specific @@ -1286,7 +1285,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="AUTOSERVICES"/>auto services (G)</term> + <term><anchor id="AUTOSERVICES">auto services (G)</term> <listitem><para>This is a synonym for the <link linkend="PRELOAD"> <parameter>preload</parameter></link>.</para> </listitem> @@ -1295,7 +1294,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="AUTHMETHODS"/>auth methods (G)</term> + <term><anchor id="AUTHMETHODS">auth methods (G)</term> <listitem><para>This option allows the administrator to chose what authentication methods <command>smbd</command> will use when authenticating a user. This option defaults to sensible values based on <link linkend="SECURITY"><parameter> @@ -1313,7 +1312,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="AVAILABLE"/>available (S)</term> + <term><anchor id="AVAILABLE">available (S)</term> <listitem><para>This parameter lets you "turn off" a service. If <parameter>available = no</parameter>, then <emphasis>ALL</emphasis> attempts to connect to the service will fail. Such failures are @@ -1327,12 +1326,12 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="BINDINTERFACESONLY"/>bind interfaces only (G)</term> + <term><anchor id="BINDINTERFACESONLY">bind interfaces only (G)</term> <listitem><para>This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests. It - affects file service <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and name service <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> in a slightly different ways.</para> + affects file service <ulink url="smbd.8.html">smbd(8)</ulink> and + name service <ulink url="nmbd.8.html">nmbd(8)</ulink> in slightly + different ways.</para> <para>For name service it causes <command>nmbd</command> to bind to ports 137 and 138 on the interfaces listed in the <link @@ -1352,9 +1351,8 @@ alias|alias|alias|alias... does defeat this simple check, however, so it must not be used seriously as a security feature for <command>nmbd</command>.</para> - <para>For file service it causes <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to bind only to the interface list - given in the <link linkend="INTERFACES"> + <para>For file service it causes <ulink url="smbd.8.html">smbd(8)</ulink> + to bind only to the interface list given in the <link linkend="INTERFACES"> interfaces</link> parameter. This restricts the networks that <command>smbd</command> will serve to packets coming in those interfaces. Note that you should not use this parameter for machines @@ -1363,9 +1361,10 @@ alias|alias|alias|alias... <para>If <parameter>bind interfaces only</parameter> is set then unless the network address <emphasis>127.0.0.1</emphasis> is added - to the <parameter>interfaces</parameter> parameter list <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>swat</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> may not work as expected due to the reasons covered below.</para> + to the <parameter>interfaces</parameter> parameter list <ulink + url="smbpasswd.8.html"><command>smbpasswd(8)</command></ulink> + and <ulink url="swat.8.html"><command>swat(8)</command></ulink> may + not work as expected due to the reasons covered below.</para> <para>To change a users SMB password, the <command>smbpasswd</command> by default connects to the <emphasis>localhost - 127.0.0.1</emphasis> @@ -1375,9 +1374,9 @@ alias|alias|alias|alias... <parameter>interfaces</parameter> parameter list then <command> smbpasswd</command> will fail to connect in it's default mode. <command>smbpasswd</command> can be forced to use the primary IP interface - of the local host by using its <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> <parameter>-r <replaceable>remote machine</replaceable></parameter> - parameter, with <replaceable>remote machine</replaceable> set + of the local host by using its <ulink url="smbpasswd.8.html#minusr"> + <parameter>-r <replaceable>remote machine</replaceable></parameter> + </ulink> parameter, with <replaceable>remote machine</replaceable> set to the IP name of the primary interface of the local host.</para> <para>The <command>swat</command> status page tries to connect with @@ -1397,10 +1396,9 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="BLOCKINGLOCKS"/>blocking locks (S)</term> - <listitem><para>This parameter controls the behavior - of <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when given a request by a client + <term><anchor id="BLOCKINGLOCKS">blocking locks (S)</term> + <listitem><para>This parameter controls the behavior of <ulink + url="smbd.8.html">smbd(8)</ulink> when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it.</para> @@ -1420,9 +1418,9 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="BLOCKSIZE"/>block size (S)</term> - <listitem><para>This parameter controls the behavior of <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when reporting disk free + <term><anchor id="BLOCKSIZE">block size (S)</term> + <listitem><para>This parameter controls the behavior of + <ulink url="smbd.8.html">smbd(8)</ulink> when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes. </para> @@ -1436,19 +1434,27 @@ alias|alias|alias|alias... <para>Changing this option does not change the disk free reporting size, just the block size unit reported to the client.</para> - </listitem> - </varlistentry> + + <para>Default: <command>block size = 1024</command></para> + <para>Example: <command>block size = 65536</command></para> + + </listitem> + </varlistentry> + + <varlistentry> - <term><anchor id="BROWSABLE"/>browsable (S)</term> + <term><anchor id="BROWSABLE">browsable (S)</term> <listitem><para>See the <link linkend="BROWSEABLE"><parameter> browseable</parameter></link>.</para></listitem> </varlistentry> + + <varlistentry> - <term><anchor id="BROWSELIST"/>browse list (G)</term> - <listitem><para>This controls whether <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will serve a browse list to + <term><anchor id="BROWSELIST">browse list (G)</term> + <listitem><para>This controls whether <ulink url="smbd.8.html"> + <command>smbd(8)</command></ulink> will serve a browse list to a client doing a <command>NetServerEnum</command> call. Normally set to <constant>yes</constant>. You should never need to change this.</para> @@ -1459,7 +1465,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="BROWSEABLE"/>browseable (S)</term> + <term><anchor id="BROWSEABLE">browseable (S)</term> <listitem><para>This controls whether this share is seen in the list of available shares in a net view and in the browse list.</para> @@ -1470,7 +1476,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CASESENSITIVE"/>case sensitive (S)</term> + <term><anchor id="CASESENSITIVE">case sensitive (S)</term> <listitem><para>See the discussion in the section <link linkend="NAMEMANGLINGSECT">NAME MANGLING</link>.</para> @@ -1481,7 +1487,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CASESIGNAMES"/>casesignames (S)</term> + <term><anchor id="CASESIGNAMES">casesignames (S)</term> <listitem><para>Synonym for <link linkend="CASESENSITIVE">case sensitive</link>.</para></listitem> </varlistentry> @@ -1489,12 +1495,12 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CHANGENOTIFYTIMEOUT"/>change notify timeout (G)</term> + <term><anchor id="CHANGENOTIFYTIMEOUT">change notify timeout (G)</term> <listitem><para>This SMB allows a client to tell a server to "watch" a particular directory for any changes and only reply to the SMB request when a change has occurred. Such constant scanning of - a directory is expensive under UNIX, hence an <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon only performs such a scan + a directory is expensive under UNIX, hence an <ulink url="smbd.8.html"> + <command>smbd(8)</command></ulink> daemon only performs such a scan on each requested directory once every <parameter>change notify timeout</parameter> seconds.</para> @@ -1507,7 +1513,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CHANGESHARECOMMAND"/>change share command (G)</term> + <term><anchor id="CHANGESHARECOMMAND">change share command (G)</term> <listitem><para>Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The <parameter>change share command</parameter> is used to define an @@ -1557,8 +1563,12 @@ alias|alias|alias|alias... </listitem> </varlistentry> + + + + <varlistentry> - <term><anchor id="COMMENT"/>comment (S)</term> + <term><anchor id="COMMENT">comment (S)</term> <listitem><para>This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via <command>net view</command> to list what shares @@ -1575,7 +1585,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CONFIGFILE"/>config file (G)</term> + <term><anchor id="CONFIGFILE">config file (G)</term> <listitem><para>This allows you to override the config file to use, instead of the default (usually <filename>smb.conf</filename>). There is a chicken and egg problem here as this option is set @@ -1599,7 +1609,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="COPY"/>copy (S)</term> + <term><anchor id="COPY">copy (S)</term> <listitem><para>This parameter allows you to "clone" service entries. The specified service is simply duplicated under the current service's name. Any parameters specified in the current @@ -1617,7 +1627,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CREATEMASK"/>create mask (S)</term> + <term><anchor id="CREATEMASK">create mask (S)</term> <listitem><para>A synonym for this parameter is <link linkend="CREATEMODE"><parameter>create mode</parameter> </link>.</para> @@ -1661,14 +1671,14 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="CREATEMODE"/>create mode (S)</term> + <term><anchor id="CREATEMODE">create mode (S)</term> <listitem><para>This is a synonym for <link linkend="CREATEMASK"><parameter> create mask</parameter></link>.</para></listitem> </varlistentry> <varlistentry> - <term><anchor id="CSCPOLICY"/>csc policy (S)</term> + <term><anchor id="CSCPOLICY">csc policy (S)</term> <listitem><para>This stands for <emphasis>client-side caching policy</emphasis>, and specifies how clients capable of offline caching will cache the files in the share. The valid values @@ -1687,7 +1697,7 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="DEADTIME"/>deadtime (G)</term> + <term><anchor id="DEADTIME">deadtime (G)</term> <listitem><para>The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected. The deadtime only takes @@ -1713,7 +1723,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEBUGHIRESTIMESTAMP"/>debug hires timestamp (G)</term> + <term><anchor id="DEBUGHIRESTIMESTAMP">debug hires timestamp (G)</term> <listitem><para>Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this boolean parameter adds microsecond resolution to the timestamp @@ -1730,7 +1740,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEBUGPID"/>debug pid (G)</term> + <term><anchor id="DEBUGPID">debug pid (G)</term> <listitem><para>When using only one log file for more then one forked <ulink url="smbd.8.html">smbd</ulink>-process there may be hard to follow which process outputs which message. This boolean parameter is adds the process-id @@ -1745,7 +1755,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEBUGTIMESTAMP"/>debug timestamp (G)</term> + <term><anchor id="DEBUGTIMESTAMP">debug timestamp (G)</term> <listitem><para>Samba debug log messages are timestamped by default. If you are running at a high <link linkend="DEBUGLEVEL"> <parameter>debug level</parameter></link> these timestamps @@ -1758,7 +1768,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEBUGUID"/>debug uid (G)</term> + <term><anchor id="DEBUGUID">debug uid (G)</term> <listitem><para>Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers @@ -1774,7 +1784,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEBUGLEVEL"/>debuglevel (G)</term> + <term><anchor id="DEBUGLEVEL">debuglevel (G)</term> <listitem><para>Synonym for <link linkend="LOGLEVEL"><parameter> log level</parameter></link>.</para> </listitem> @@ -1783,7 +1793,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEFAULT"/>default (G)</term> + <term><anchor id="DEFAULT">default (G)</term> <listitem><para>A synonym for <link linkend="DEFAULTSERVICE"><parameter> default service</parameter></link>.</para></listitem> </varlistentry> @@ -1791,7 +1801,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEFAULTCASE"/>default case (S)</term> + <term><anchor id="DEFAULTCASE">default case (S)</term> <listitem><para>See the section on <link linkend="NAMEMANGLINGSECT"> NAME MANGLING</link>. Also note the <link linkend="SHORTPRESERVECASE"> <parameter>short preserve case</parameter></link> parameter.</para> @@ -1803,7 +1813,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEFAULTDEVMODE"/>default devmode (S)</term> + <term><anchor id="DEFAULTDEVMODE">default devmode (S)</term> <listitem><para>This parameter is only applicable to <link linkend="PRINTOK">printable</link> services. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba @@ -1841,7 +1851,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DEFAULTSERVICE"/>default service (G)</term> + <term><anchor id="DEFAULTSERVICE">default service (G)</term> <listitem><para>This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found. Note that the square brackets are <emphasis>NOT</emphasis> @@ -1867,27 +1877,24 @@ alias|alias|alias|alias... <para>Example:</para> -<para><programlisting> + <para><programlisting> [global] default service = pub [pub] path = /%S -</programlisting></para> + </programlisting></para> </listitem> </varlistentry> - <varlistentry><term><anchor id="DELETEGROUPSCRIPT"/>delete group script (G)</term> + <varlistentry><term><anchor id="DELETEGROUPSCRIPT">delete group script (G)</term> <listitem><para>This is the full pathname to a script that will - be run <emphasis>AS ROOT</emphasis> <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when a group is requested to be deleted. - It will expand any <parameter>%g</parameter> to the group name passed. - This script is only useful for installations using the Windows NT domain administration tools. + be run <emphasis>AS ROOT</emphasis> by <ulink url="smbd.8.html">smbd(8)</ulink> when a group is requested to be deleted. It will expand any <parameter>%g</parameter> to the group name passed. This script is only useful for installations using the Windows NT domain administration tools. </para></listitem> </varlistentry> <varlistentry> - <term><anchor id="DELETEPRINTERCOMMAND"/>deleteprinter command (G)</term> + <term><anchor id="DELETEPRINTERCOMMAND">deleteprinter command (G)</term> <listitem><para>With the introduction of MS-RPC based printer support for Windows NT/2000 clients in Samba 2.2, it is now possible to delete printer at run time by issuing the @@ -1913,7 +1920,7 @@ alias|alias|alias|alias... <para>See also <link linkend="ADDPRINTERCOMMAND"><parameter> addprinter command</parameter></link>, <link - linkend="PRINTING"><parameter>printing</parameter></link>, + linkend="printing"><parameter>printing</parameter></link>, <link linkend="SHOWADDPRINTERWIZARD"><parameter>show add printer wizard</parameter></link></para> @@ -1929,7 +1936,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DELETEREADONLY"/>delete readonly (S)</term> + <term><anchor id="DELETEREADONLY">delete readonly (S)</term> <listitem><para>This parameter allows readonly files to be deleted. This is not normal DOS semantics, but is allowed by UNIX.</para> @@ -1943,7 +1950,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DELETESHARECOMMAND"/>delete share command (G)</term> + <term><anchor id="DELETESHARECOMMAND">delete share command (G)</term> <listitem><para>Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The <parameter>delete share command</parameter> is used to define an @@ -1991,11 +1998,10 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DELETEUSERSCRIPT"/>delete user script (G)</term> + <term><anchor id="DELETEUSERSCRIPT">delete user script (G)</term> <listitem><para>This is the full pathname to a script that will - be run by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when managing users - with remote RPC (NT) tools. + be run by <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> + when managing user's with remote RPC (NT) tools. </para> <para>This script is called when a remote client removes a user @@ -2013,13 +2019,13 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="DELETEUSERFROMGROUPSCRIPT"/>delete user from group script (G)</term> + <term><anchor id="DELETEUSERFROMGROUPSCRIPT">delete user from group script (G)</term> <listitem><para>Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration - tools. It will be run by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> <emphasis>AS ROOT</emphasis>. - Any <parameter>%g</parameter> will be replaced with the group name and - any <parameter>%u</parameter> will be replaced with the user name. + tools. It will be run by <ulink url="smbd.8.html">smbd(8)</ulink> + <emphasis>AS ROOT</emphasis>. Any <parameter>%g</parameter> will be + replaced with the group name and any <parameter>%u</parameter> will + be replaced with the user name. </para> <para>Default: <command>delete user from group script = </command></para> @@ -2030,7 +2036,7 @@ alias|alias|alias|alias... </varlistentry> <varlistentry> - <term><anchor id="DELETEVETOFILES"/>delete veto files (S)</term> + <term><anchor id="DELETEVETOFILES">delete veto files (S)</term> <listitem><para>This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the <link linkend="VETOFILES"><parameter>veto files</parameter></link> @@ -2059,7 +2065,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DENYHOSTS"/>deny hosts (S)</term> + <term><anchor id="DENYHOSTS">deny hosts (S)</term> <listitem><para>Synonym for <link linkend="HOSTSDENY"><parameter>hosts deny</parameter></link>.</para></listitem> </varlistentry> @@ -2068,7 +2074,7 @@ alias|alias|alias|alias... <varlistentry> - <term><anchor id="DFREECOMMAND"/>dfree command (G)</term> + <term><anchor id="DFREECOMMAND">dfree command (G)</term> <listitem><para>The <parameter>dfree command</parameter> setting should only be used on systems where a problem occurs with the internal disk space calculations. This has been known to happen with Ultrix, @@ -2101,17 +2107,17 @@ alias|alias|alias|alias... <para>Where the script dfree (which must be made executable) could be:</para> -<para><programlisting> -#!/bin/sh -df $1 | tail -1 | awk '{print $2" "$4}' -</programlisting></para> + <para><programlisting> + #!/bin/sh + df $1 | tail -1 | awk '{print $2" "$4}' + </programlisting></para> <para>or perhaps (on Sys V based systems):</para> -<para><programlisting> -#!/bin/sh -/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' -</programlisting></para> + <para><programlisting> + #!/bin/sh + /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' + </programlisting></para> <para>Note that you may have to replace the command names with full path names on some systems.</para> @@ -2122,7 +2128,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DIRECTORY"/>directory (S)</term> + <term><anchor id="DIRECTORY">directory (S)</term> <listitem><para>Synonym for <link linkend="PATH"><parameter>path </parameter></link>.</para></listitem> </varlistentry> @@ -2130,7 +2136,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DIRECTORYMASK"/>directory mask (S)</term> + <term><anchor id="DIRECTORYMASK">directory mask (S)</term> <listitem><para>This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories.</para> @@ -2178,7 +2184,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DIRECTORYMODE"/>directory mode (S)</term> + <term><anchor id="DIRECTORYMODE">directory mode (S)</term> <listitem><para>Synonym for <link linkend="DIRECTORYMASK"><parameter> directory mask</parameter></link></para></listitem> </varlistentry> @@ -2186,7 +2192,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DIRECTORYSECURITYMASK"/>directory security mask (S)</term> + <term><anchor id="DIRECTORYSECURITYMASK">directory security mask (S)</term> <listitem><para>This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog @@ -2221,7 +2227,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DISABLENETBIOS"/>disable netbios (G)</term> + <term><anchor id="DISABLENETBIOS">disable netbios (G)</term> <listitem><para>Enabling this parameter will disable netbios support in Samba. Netbios is the only available form of browsing in all windows versions except for 2000 and XP. </para> @@ -2236,7 +2242,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="DISABLESPOOLSS"/>disable spoolss (G)</term> + <term><anchor id="DISABLESPOOLSS">disable spoolss (G)</term> <listitem><para>Enabling this parameter will disable Samba's support for the SPOOLSS set of MS-RPC's and will yield identical behavior as Samba 2.0.x. Windows NT/2000 clients will downgrade to using @@ -2257,7 +2263,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="DISPLAYCHARSET"/>display charset (G)</term> + <term><anchor id="DISPLAYCHARSET">display charset (G)</term> <listitem><para>Specifies the charset that samba will use to print messages to stdout and stderr and SWAT will use. Should generally be the same as the <command>unix charset</command>. @@ -2272,12 +2278,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DNSPROXY"/>dns proxy (G)</term> - <listitem><para>Specifies that <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when acting as a WINS server and - finding that a NetBIOS name has not been registered, should treat the - NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server - for that name on behalf of the name-querying client.</para> + <term><anchor id="DNSPROXY">dns proxy (G)</term> + <listitem><para>Specifies that <ulink url="nmbd.8.html">nmbd(8)</ulink> + when acting as a WINS server and finding that a NetBIOS name has not + been registered, should treat the NetBIOS name word-for-word as a DNS + name and do a lookup with the DNS server for that name on behalf of + the name-querying client.</para> <para>Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be @@ -2295,7 +2301,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DOMAINLOGONS"/>domain logons (G)</term> + <term><anchor id="DOMAINLOGONS">domain logons (G)</term> <listitem><para>If set to <constant>yes</constant>, the Samba server will serve Windows 95/98 Domain logons for the <link linkend="WORKGROUP"> <parameter>workgroup</parameter></link> it is in. Samba 2.2 @@ -2310,20 +2316,20 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DOMAINMASTER"/>domain master (G)</term> - <listitem><para>Tell <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to enable WAN-wide browse list + <term><anchor id="DOMAINMASTER">domain master (G)</term> + <listitem><para>Tell <ulink url="nmbd.8.html"><command> + nmbd(8)</command></ulink> to enable WAN-wide browse list collation. Setting this option causes <command>nmbd</command> to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given <link linkend="WORKGROUP"> <parameter>workgroup</parameter></link>. Local master browsers in the same <parameter>workgroup</parameter> on broadcast-isolated subnets will give this <command>nmbd</command> their local browse lists, - and then ask <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> for a complete copy of the browse - list for the whole wide area network. Browser clients will then contact - their local master browser, and will receive the domain-wide browse list, - instead of just the list for their broadcast-isolated subnet.</para> + and then ask <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> + for a complete copy of the browse list for the whole wide area + network. Browser clients will then contact their local master browser, + and will receive the domain-wide browse list, instead of just the list + for their broadcast-isolated subnet.</para> <para>Note that Windows NT Primary Domain Controllers expect to be able to claim this <parameter>workgroup</parameter> specific special @@ -2348,7 +2354,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DONTDESCEND"/>dont descend (S)</term> + <term><anchor id="DONTDESCEND">dont descend (S)</term> <listitem><para>There are certain directories on some systems (e.g., the <filename>/proc</filename> tree under Linux) that are either not of interest to clients or are infinitely deep (recursive). This @@ -2367,7 +2373,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="DOSCHARSET"/>dos charset (G)</term> + <term><anchor id="DOSCHARSET">dos charset (G)</term> <listitem><para>DOS SMB clients assume the server has the same charset as they do. This option specifies which charset Samba should talk to DOS clients. @@ -2375,14 +2381,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>The default depends on which charsets you have instaled. Samba tries to use charset 850 but falls back to ASCII in - case it is not available. Run <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> to check the default on your system. + case it is not available. Run <ulink url="testparm.1.html">testparm(1) + </ulink> to check the default on your system. </para> </listitem> </varlistentry> <varlistentry> - <term><anchor id="DOSFILEMODE"/>dos filemode (S)</term> + <term><anchor id="DOSFILEMODE">dos filemode (S)</term> <listitem><para> The default behavior in Samba is to provide UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it. However, this behavior @@ -2401,13 +2407,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DOSFILETIMERESOLUTION"/>dos filetime resolution (S)</term> + <term><anchor id="DOSFILETIMERESOLUTION">dos filetime resolution (S)</term> <listitem><para>Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second - resolution is made to <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>.</para> + resolution is made to <ulink url="smbd.8.html"><command>smbd(8)</command> + </ulink>.</para> <para>This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. If oplocks are enabled on a @@ -2427,15 +2433,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="DOSFILETIMES"/>dos filetimes (S)</term> + <term><anchor id="DOSFILETIMES">dos filetimes (S)</term> <listitem><para>Under DOS and Windows, if a user can write to a file they can change the timestamp on it. Under POSIX semantics, only the owner of the file or root may change the timestamp. By default, Samba runs with POSIX semantics and refuses to change the timestamp on a file if the user <command>smbd</command> is acting on behalf of is not the file owner. Setting this option to <constant> - yes</constant> allows DOS semantics and <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will change the file + yes</constant> allows DOS semantics and <ulink url="smbd.8.html">smbd</ulink> will change the file timestamp as DOS requires.</para> <para>Default: <command>dos filetimes = no</command></para></listitem> @@ -2444,7 +2449,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="ENCRYPTPASSWORDS"/>encrypt passwords (G)</term> + <term><anchor id="ENCRYPTPASSWORDS">encrypt passwords (G)</term> <listitem><para>This boolean controls whether encrypted passwords will be negotiated with the client. Note that Windows NT 4.0 SP3 and above and also Windows 98 will by default expect encrypted passwords @@ -2453,11 +2458,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' directory <filename>docs/</filename> shipped with the source code.</para> <para>In order for encrypted passwords to work correctly - <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> must either - have access to a local <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file (see the <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> program for information on how to set up + <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> must either + have access to a local <ulink url="smbpasswd.5.html"><filename>smbpasswd(5) + </filename></ulink> file (see the <ulink url="smbpasswd.8.html"><command> + smbpasswd(8)</command></ulink> program for information on how to set up and maintain this file), or set the <link linkend="SECURITY">security = [server|domain|ads]</link> parameter which causes <command>smbd</command> to authenticate against another @@ -2468,7 +2472,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="ENHANCEDBROWSING"/>enhanced browsing (G)</term> + <term><anchor id="ENHANCEDBROWSING">enhanced browsing (G)</term> <listitem><para>This option enables a couple of enhancements to cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations. @@ -2494,7 +2498,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="ENUMPORTSCOMMAND"/>enumports command (G)</term> + <term><anchor id="ENUMPORTSCOMMAND">enumports command (G)</term> <listitem><para>The concept of a "port" is fairly foreign to UNIX hosts. Under Windows NT/2000 print servers, a port is associated with a port monitor and generally takes the form of @@ -2517,7 +2521,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="EXEC"/>exec (S)</term> + <term><anchor id="EXEC">exec (S)</term> <listitem><para>This is a synonym for <link linkend="PREEXEC"> <parameter>preexec</parameter></link>.</para></listitem> </varlistentry> @@ -2525,7 +2529,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FAKEDIRECTORYCREATETIMES"/>fake directory create times (S)</term> + <term><anchor id="FAKEDIRECTORYCREATETIMES">fake directory create times (S)</term> <listitem><para>NTFS and Windows VFAT file systems keep a create time for all files and directories. This is not the same as the ctime - status change time - that Unix keeps, so Samba by default @@ -2559,7 +2563,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FAKEOPLOCKS"/>fake oplocks (S)</term> + <term><anchor id="FAKEOPLOCKS">fake oplocks (S)</term> <listitem><para>Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock (opportunistic lock) then the client is free to assume @@ -2591,11 +2595,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FOLLOWSYMLINKS"/>follow symlinks (S)</term> + <term><anchor id="FOLLOWSYMLINKS">follow symlinks (S)</term> <listitem><para>This parameter allows the Samba administrator - to stop <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> from following symbolic - links in a particular share. Setting this + to stop <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> + from following symbolic links in a particular share. Setting this parameter to <constant>no</constant> prevents any file or directory that is a symbolic link from being followed (the user will get an error). This option is very useful to stop users from adding a @@ -2612,7 +2615,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FORCECREATEMODE"/>force create mode (S)</term> + <term><anchor id="FORCECREATEMODE">force create mode (S)</term> <listitem><para>This parameter specifies a set of UNIX mode bit permissions that will <emphasis>always</emphasis> be set on a file created by Samba. This is done by bitwise 'OR'ing these bits onto @@ -2640,7 +2643,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FORCEDIRECTORYMODE"/>force directory mode (S)</term> + <term><anchor id="FORCEDIRECTORYMODE">force directory mode (S)</term> <listitem><para>This parameter specifies a set of UNIX mode bit permissions that will <emphasis>always</emphasis> be set on a directory created by Samba. This is done by bitwise 'OR'ing these bits onto the @@ -2669,7 +2672,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FORCEDIRECTORYSECURITYMODE"/>force directory security mode (S)</term> + <term><anchor id="FORCEDIRECTORYSECURITYMODE">force directory security mode (S)</term> <listitem><para>This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box.</para> @@ -2705,7 +2708,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FORCEGROUP"/>force group (S)</term> + <term><anchor id="FORCEGROUP">force group (S)</term> <listitem><para>This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. This is useful for sharing files by ensuring @@ -2741,7 +2744,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="FORCESECURITYMODE"/>force security mode (S)</term> + <term><anchor id="FORCESECURITYMODE">force security mode (S)</term> <listitem><para>This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog @@ -2779,7 +2782,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FORCEUSER"/>force user (S)</term> + <term><anchor id="FORCEUSER">force user (S)</term> <listitem><para>This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. You should also use it carefully @@ -2807,11 +2810,11 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="FSTYPE"/>fstype (S)</term> + <term><anchor id="FSTYPE">fstype (S)</term> <listitem><para>This parameter allows the administrator to configure the string that specifies the type of filesystem a share - is using that is reported by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when a client queries the filesystem type + is using that is reported by <ulink url="smbd.8.html"><command>smbd(8) + </command></ulink> when a client queries the filesystem type for a share. The default type is <constant>NTFS</constant> for compatibility with Windows NT but this can be changed to other strings such as <constant>Samba</constant> or <constant>FAT @@ -2824,7 +2827,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="GETWDCACHE"/>getwd cache (G)</term> + <term><anchor id="GETWDCACHE">getwd cache (G)</term> <listitem><para>This is a tuning option. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls. This can have a significant impact on performance, especially @@ -2838,7 +2841,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="GROUP"/>group (S)</term> + <term><anchor id="GROUP">group (S)</term> <listitem><para>Synonym for <link linkend="FORCEGROUP"><parameter>force group</parameter></link>.</para></listitem> </varlistentry> @@ -2846,7 +2849,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="GUESTACCOUNT"/>guest account (S)</term> + <term><anchor id="GUESTACCOUNT">guest account (S)</term> <listitem><para>This is a username which will be used for access to services which are specified as <link linkend="GUESTOK"><parameter> guest ok</parameter></link> (see below). Whatever privileges this @@ -2876,16 +2879,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="GUESTOK"/>guest ok (S)</term> + <term><anchor id="GUESTOK">guest ok (S)</term> <listitem><para>If this parameter is <constant>yes</constant> for a service, then no password is required to connect to the service. Privileges will be those of the <link linkend="GUESTACCOUNT"><parameter> guest account</parameter></link>.</para> - <para>This paramater nullifies the benifits of setting - <link linkend="RESTRICTANONYMOUS"><parameter>restrict - anonymous</parameter></link> = 2</para> - <para>See the section below on <link linkend="SECURITY"><parameter> security</parameter></link> for more information about this option. </para> @@ -2896,7 +2895,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="GUESTONLY"/>guest only (S)</term> + <term><anchor id="GUESTONLY">guest only (S)</term> <listitem><para>If this parameter is <constant>yes</constant> for a service, then only guest connections to the service are permitted. This parameter will have no effect if <link linkend="GUESTOK"> @@ -2912,7 +2911,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HIDEDOTFILES"/>hide dot files (S)</term> + <term><anchor id="HIDEDOTFILES">hide dot files (S)</term> <listitem><para>This is a boolean parameter that controls whether files starting with a dot appear as hidden files.</para> @@ -2922,7 +2921,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HIDEFILES"/>hide files(S)</term> + <term><anchor id="HIDEFILES">hide files(S)</term> <listitem><para>This is a list of files or directories that are not visible but are accessible. The DOS 'hidden' attribute is applied to any files or directories that match.</para> @@ -2960,7 +2959,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HIDELOCALUSERS"/>hide local users(G)</term> + <term><anchor id="HIDELOCALUSERS">hide local users(G)</term> <listitem><para>This parameter toggles the hiding of local UNIX users (root, wheel, floppy, etc) from remote clients.</para> @@ -2970,7 +2969,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HIDEUNREADABLE"/>hide unreadable (G)</term> + <term><anchor id="HIDEUNREADABLE">hide unreadable (G)</term> <listitem><para>This parameter prevents clients from seeing the existance of files that cannot be read. Defaults to off.</para> @@ -2979,7 +2978,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="HIDEUNWRITEABLEFILES"/>hide unwriteable files (G)</term> + <term><anchor id="HIDEUNWRITEABLEFILES">hide unwriteable files (G)</term> <listitem><para>This parameter prevents clients from seeing the existance of files that cannot be written to. Defaults to off. Note that unwriteable directories are shown as usual. @@ -2990,7 +2989,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="HIDESPECIALFILES"/>hide special files (G)</term> + <term><anchor id="HIDESPECIALFILES">hide special files (G)</term> <listitem><para>This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings. @@ -3001,10 +3000,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="HOMEDIRMAP"/>homedir map (G)</term> + <term><anchor id="HOMEDIRMAP">homedir map (G)</term> <listitem><para>If<link linkend="NISHOMEDIR"><parameter>nis homedir - </parameter></link> is <constant>yes</constant>, and <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> is also acting + </parameter></link> is <constant>yes</constant>, and <ulink + url="smbd.8.html"><command>smbd(8)</command></ulink> is also acting as a Win95/98 <parameter>logon server</parameter> then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted. At present, only the Sun @@ -3034,7 +3033,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HOSTMSDFS"/>host msdfs (G)</term> + <term><anchor id="HOSTMSDFS">host msdfs (G)</term> <listitem><para>This boolean parameter is only available if Samba has been configured and compiled with the <command> --with-msdfs</command> option. If set to <constant>yes</constant>, @@ -3052,7 +3051,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="HOSTNAMELOOKUPS"/>hostname lookups (G)</term> + <term><anchor id="HOSTNAMELOOKUPS">hostname lookups (G)</term> <listitem><para>Specifies whether samba should use (expensive) hostname lookups or use the ip addresses instead. An example place where hostname lookups are currently used is when checking @@ -3068,7 +3067,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HOSTSALLOW"/>hosts allow (S)</term> + <term><anchor id="HOSTSALLOW">hosts allow (S)</term> <listitem><para>A synonym for this parameter is <parameter>allow hosts</parameter>.</para> @@ -3117,9 +3116,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>Note that access still requires suitable user-level passwords.</para> - <para>See <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> for a way of testing your host access - to see if it does what you expect.</para> + <para>See <ulink url="testparm.1.html"><command>testparm(1)</command> + </ulink> for a way of testing your host access to see if it does + what you expect.</para> <para>Default: <emphasis>none (i.e., all hosts permitted access) </emphasis></para> @@ -3132,7 +3131,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HOSTSDENY"/>hosts deny (S)</term> + <term><anchor id="HOSTSDENY">hosts deny (S)</term> <listitem><para>The opposite of <parameter>hosts allow</parameter> - hosts listed here are <emphasis>NOT</emphasis> permitted access to services unless the specific services have their own lists to override @@ -3149,7 +3148,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="HOSTSEQUIV"/>hosts equiv (G)</term> + <term><anchor id="HOSTSEQUIV">hosts equiv (G)</term> <listitem><para>If this global parameter is a non-null string, it specifies the name of a file to read for the names of hosts and users who will be allowed access without specifying a password. @@ -3178,7 +3177,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="INCLUDE"/>include (G)</term> + <term><anchor id="INCLUDE">include (G)</term> <listitem><para>This allows you to include one config file inside another. The file is included literally, as though typed in place.</para> @@ -3195,7 +3194,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="INHERITACLS"/>inherit acls (S)</term> + <term><anchor id="INHERITACLS">inherit acls (S)</term> <listitem><para>This parameter can be used to ensure that if default acls exist on parent directories, they are always honored when creating a subdirectory. @@ -3213,7 +3212,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="INHERITPERMISSIONS"/>inherit permissions (S)</term> + <term><anchor id="INHERITPERMISSIONS">inherit permissions (S)</term> <listitem><para>The permissions on new files and directories are normally governed by <link linkend="CREATEMASK"><parameter> create mask</parameter></link>, <link linkend="DIRECTORYMASK"> @@ -3254,7 +3253,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="INTERFACES"/>interfaces (G)</term> + <term><anchor id="INTERFACES">interfaces (G)</term> <listitem><para>This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NBT traffic. By default Samba will query @@ -3306,7 +3305,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="INVALIDUSERS"/>invalid users (S)</term> + <term><anchor id="INVALIDUSERS">invalid users (S)</term> <listitem><para>This is a list of users that should not be allowed to login to this service. This is really a <emphasis>paranoid</emphasis> check to absolutely ensure an improper setting does not breach @@ -3318,12 +3317,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>A name starting with '+' is interpreted only by looking in the UNIX group database. A name starting with - '&' is interpreted only by looking in the NIS netgroup database + '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters - '+' and '&' may be used at the start of the name in either order + '+' and '&' may be used at the start of the name in either order so the value <parameter>+&group</parameter> means check the UNIX group database, followed by the NIS netgroup database, and - the value <parameter>&+group</parameter> means check the NIS + the value <parameter>&+group</parameter> means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix).</para> @@ -3342,7 +3341,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="KEEPALIVE"/>keepalive (G)</term> + <term><anchor id="KEEPALIVE">keepalive (G)</term> <listitem><para>The value of the parameter (an integer) represents the number of seconds between <parameter>keepalive</parameter> packets. If this parameter is zero, no keepalive packets will be @@ -3362,7 +3361,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="KERNELOPLOCKS"/>kernel oplocks (G)</term> + <term><anchor id="KERNELOPLOCKS">kernel oplocks (G)</term> <listitem><para>For UNIXes that support kernel based <link linkend="OPLOCKS"><parameter>oplocks</parameter></link> (currently only IRIX and the Linux 2.4 kernel), this parameter @@ -3370,10 +3369,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>Kernel oplocks support allows Samba <parameter>oplocks </parameter> to be broken whenever a local UNIX process or NFS operation - accesses a file that <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> has oplocked. This allows complete - data consistency between SMB/CIFS, NFS and local file access (and is - a <emphasis>very</emphasis> cool feature :-).</para> + accesses a file that <ulink url="smbd.8.html"><command>smbd(8)</command> + </ulink> has oplocked. This allows complete data consistency between + SMB/CIFS, NFS and local file access (and is a <emphasis>very</emphasis> + cool feature :-).</para> <para>This parameter defaults to <constant>on</constant>, but is translated to a no-op on systems that no not have the necessary kernel support. @@ -3391,12 +3390,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LANMANAUTH"/>lanman auth (G)</term> - <listitem><para>This parameter determines whether or not <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will attempt to authenticate users - using the LANMAN password hash. If disabled, only clients which support NT - password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not - Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.</para> + <term><anchor id="LANMANAUTH">lanman auth (G)</term> + <listitem><para>This parameter determines whether or not <ulink url="smbd.8.html">smbd</ulink> will + attempt to authenticate users using the LANMAN password hash. + If disabled, only clients which support NT password hashes (e.g. Windows + NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS + network client) will be able to connect to the Samba host.</para> <para>Default : <command>lanman auth = yes</command></para> </listitem> @@ -3407,10 +3406,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LARGEREADWRITE"/>large readwrite (G)</term> - <listitem><para>This parameter determines whether or not <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> supports the new 64k streaming - read and write varient SMB requests introduced + <term><anchor id="LARGEREADWRITE">large readwrite (G)</term> + <listitem><para>This parameter determines whether or not <ulink url="smbd.8.html">smbd</ulink> + supports the new 64k streaming read and write varient SMB requests introduced with Windows 2000. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64-bit capable operating system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with @@ -3425,15 +3423,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPADMINDN"/>ldap admin dn (G)</term> + <term><anchor id="LDAPADMINDN">ldap admin dn (G)</term> <listitem><para> The <parameter>ldap admin dn</parameter> defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information. The <parameter>ldap admin dn</parameter> is used in conjunction with the admin dn password stored in the <filename>private/secrets.tdb</filename> file. See the - <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> man page for more information on how - to accmplish this. + <ulink url="smbpasswd.8.html"><command>smbpasswd(8)</command></ulink> man + page for more information on how to accmplish this. </para> <varlistentry> @@ -3451,7 +3448,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPFILTER"/>ldap filter (G)</term> + <term><anchor id="LDAPFILTER">ldap filter (G)</term> <listitem><para>This parameter specifies the RFC 2254 compliant LDAP search filter. The default is to match the login name with the <constant>uid</constant> attribute for all entries matching the <constant>sambaAccount</constant> @@ -3465,7 +3462,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPPORT"/>ldap port (G)</term> + <term><anchor id="LDAPPORT">ldap port (G)</term> <listitem><para>This parameter is only available if Samba has been configure to include the <command>--with-ldapsam</command> option at compile time. @@ -3487,7 +3484,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPSERVER"/>ldap server (G)</term> + <term><anchor id="LDAPSERVER">ldap server (G)</term> <listitem><para>This parameter is only available if Samba has been configure to include the <command>--with-ldapsam</command> option at compile time. @@ -3504,7 +3501,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPSSL"/>ldap ssl (G)</term> + <term><anchor id="LDAPSSL">ldap ssl (G)</term> <listitem><para>This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is <emphasis>NOT</emphasis> related to @@ -3538,7 +3535,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPSUFFIX"/>ldap suffix (G)</term> + <term><anchor id="LDAPSUFFIX">ldap suffix (G)</term> <listitem> <para>Specifies where user and machine accounts are added to the tree. Can be overriden by <command>ldap user suffix</command> and <command>ldap machine suffix</command>. It also used as the base dn for all ldap searches. </para> @@ -3549,7 +3546,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPUSERSUFFIX"/>ldap user suffix (G)</term> + <term><anchor id="LDAPUSERSUFFIX">ldap user suffix (G)</term> <listitem><para>It specifies where users are added to the tree. </para> @@ -3562,7 +3559,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LDAPMACHINESUFFIX"/>ldap machine suffix (G)</term> + <term><anchor id="LDAPMACHINESUFFIX">ldap machine suffix (G)</term> <listitem><para>It specifies where machines should be added to the ldap tree. </para> @@ -3574,7 +3571,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="LDAPPASSWDSYNC"/>ldap passwd sync (G)</term> + <term><anchor id="LDAPPASSWDSYNC">ldap passwd sync (G)</term> <listitem><para>This option is used to define whether or not Samba should sync the LDAP password with the NT and LM hashes for normal accounts (NOT for @@ -3598,7 +3595,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="LDAPTRUSTIDS"/>ldap trust ids (G)</term> + <term><anchor id="LDAPTRUSTIDS">ldap trust ids (G)</term> <listitem><para>Normally, Samba validates each entry in the LDAP server against getpwnam(). This allows LDAP to be used for Samba with the unix system using @@ -3617,7 +3614,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="LEVEL2OPLOCKS"/>level2 oplocks (S)</term> + <term><anchor id="LEVEL2OPLOCKS">level2 oplocks (S)</term> <listitem><para>This parameter controls whether Samba supports level2 (read-only) oplocks on a share.</para> @@ -3661,9 +3658,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LMANNOUNCE"/>lm announce (G)</term> - <listitem><para>This parameter determines if <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will produce Lanman announce + <term><anchor id="LMANNOUNCE">lm announce (G)</term> + <listitem><para>This parameter determines if <ulink url="nmbd.8.html"> + <command>nmbd(8)</command></ulink> will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list. This parameter can have three values, <constant>yes</constant>, <constant>no</constant>, or @@ -3688,7 +3685,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LMINTERVAL"/>lm interval (G)</term> + <term><anchor id="LMINTERVAL">lm interval (G)</term> <listitem><para>If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the <link linkend="LMANNOUNCE"> <parameter>lm announce</parameter></link> parameter) then this @@ -3708,7 +3705,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOADPRINTERS"/>load printers (G)</term> + <term><anchor id="LOADPRINTERS">load printers (G)</term> <listitem><para>A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default. See the <link linkend="PRINTERSSECT">printers</link> section for @@ -3721,9 +3718,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOCALMASTER"/>local master (G)</term> - <listitem><para>This option allows <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to try and become a local master browser + <term><anchor id="LOCALMASTER">local master (G)</term> + <listitem><para>This option allows <ulink url="nmbd.8.html"><command> + nmbd(8)</command></ulink> to try and become a local master browser on a subnet. If set to <constant>no</constant> then <command> nmbd</command> will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By @@ -3742,7 +3739,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOCKDIR"/>lock dir (G)</term> + <term><anchor id="LOCKDIR">lock dir (G)</term> <listitem><para>Synonym for <link linkend="LOCKDIRECTORY"><parameter> lock directory</parameter></link>.</para></listitem> </varlistentry> @@ -3750,7 +3747,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOCKDIRECTORY"/>lock directory (G)</term> + <term><anchor id="LOCKDIRECTORY">lock directory (G)</term> <listitem><para>This option specifies the directory where lock files will be placed. The lock files are used to implement the <link linkend="MAXCONNECTIONS"><parameter>max connections</parameter> @@ -3764,7 +3761,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOCKSPINCOUNT"/>lock spin count (G)</term> + <term><anchor id="LOCKSPINCOUNT">lock spin count (G)</term> <listitem><para>This parameter controls the number of times that smbd should attempt to gain a byte range lock on the behalf of a client request. Experiments have shown that @@ -3783,7 +3780,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOCKSPINTIME"/>lock spin time (G)</term> + <term><anchor id="LOCKSPINTIME">lock spin time (G)</term> <listitem><para>The time in microseconds that smbd should pause before attempting to gain a failed lock. See <link linkend="LOCKSPINCOUNT"><parameter>lock spin @@ -3797,7 +3794,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOCKING"/>locking (S)</term> + <term><anchor id="LOCKING">locking (S)</term> <listitem><para>This controls whether or not locking will be performed by the server in response to lock requests from the client.</para> @@ -3825,7 +3822,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOGFILE"/>log file (G)</term> + <term><anchor id="LOGFILE">log file (G)</term> <listitem><para>This option allows you to override the name of the Samba log file (also known as the debug file).</para> @@ -3839,7 +3836,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOGLEVEL"/>log level (G)</term> + <term><anchor id="LOGLEVEL">log level (G)</term> <listitem><para>The value of the parameter (a astring) allows the debug level (logging level) to be specified in the <filename>smb.conf</filename> file. This parameter has been @@ -3857,7 +3854,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOGONDRIVE"/>logon drive (G)</term> + <term><anchor id="LOGONDRIVE">logon drive (G)</term> <listitem><para>This parameter specifies the local path to which the home directory will be connected (see <link linkend="LOGONHOME"><parameter>logon home</parameter></link>) @@ -3874,7 +3871,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOGONHOME"/>logon home (G)</term> + <term><anchor id="LOGONHOME">logon home (G)</term> <listitem><para>This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do </para> @@ -3916,7 +3913,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOGONPATH"/>logon path (G)</term> + <term><anchor id="LOGONPATH">logon path (G)</term> <listitem><para>This parameter specifies the home directory where roaming profiles (NTuser.dat etc files for Windows NT) are stored. Contrary to previous versions of these manual pages, it has @@ -3964,7 +3961,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LOGONSCRIPT"/>logon script (G)</term> + <term><anchor id="LOGONSCRIPT">logon script (G)</term> <listitem><para>This parameter specifies the batch file (.bat) or NT command file (.cmd) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS @@ -4006,7 +4003,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LPPAUSECOMMAND"/>lppause command (S)</term> + <term><anchor id="LPPAUSECOMMAND">lppause command (S)</term> <listitem><para>This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job.</para> @@ -4050,7 +4047,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LPQCACHETIME"/>lpq cache time (G)</term> + <term><anchor id="LPQCACHETIME">lpq cache time (G)</term> <listitem><para>This controls how long lpq info will be cached for to prevent the <command>lpq</command> command being called too often. A separate cache is kept for each variation of the <command> @@ -4079,7 +4076,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LPQCOMMAND"/>lpq command (S)</term> + <term><anchor id="LPQCOMMAND">lpq command (S)</term> <listitem><para>This parameter specifies the command to be executed on the server host in order to obtain <command>lpq </command>-style printer status information.</para> @@ -4123,7 +4120,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LPRESUMECOMMAND"/>lpresume command (S)</term> + <term><anchor id="LPRESUMECOMMAND">lpresume command (S)</term> <listitem><para>This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job.</para> @@ -4163,7 +4160,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="LPRMCOMMAND"/>lprm command (S)</term> + <term><anchor id="LPRMCOMMAND">lprm command (S)</term> <listitem><para>This parameter specifies the command to be executed on the server host in order to delete a print job.</para> @@ -4193,7 +4190,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MACHINEPASSWORDTIMEOUT"/>machine password timeout (G)</term> + <term><anchor id="MACHINEPASSWORDTIMEOUT">machine password timeout (G)</term> <listitem><para>If a Samba server is a member of a Windows NT Domain (see the <link linkend="SECURITYEQUALSDOMAIN">security = domain</link>) parameter) then periodically a running <ulink url="smbd.8.html"> @@ -4203,8 +4200,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' will be changed, in seconds. The default is one week (expressed in seconds), the same as a Windows NT Domain member server.</para> - <para>See also <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, and the <link linkend="SECURITYEQUALSDOMAIN"> + <para>See also <ulink url="smbpasswd.8.html"><command>smbpasswd(8) + </command></ulink>, and the <link linkend="SECURITYEQUALSDOMAIN"> security = domain</link>) parameter.</para> <para>Default: <command>machine password timeout = 604800</command></para> @@ -4213,7 +4210,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAGICOUTPUT"/>magic output (S)</term> + <term><anchor id="MAGICOUTPUT">magic output (S)</term> <listitem><para>This parameter specifies the name of a file which will contain output created by a magic script (see the <link linkend="MAGICSCRIPT"><parameter>magic script</parameter></link> @@ -4233,7 +4230,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAGICSCRIPT"/>magic script (S)</term> + <term><anchor id="MAGICSCRIPT">magic script (S)</term> <listitem><para>This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed. This allows a UNIX script to be sent to the Samba host and @@ -4264,7 +4261,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MANGLECASE"/>mangle case (S)</term> + <term><anchor id="MANGLECASE">mangle case (S)</term> <listitem><para>See the section on <link linkend="NAMEMANGLINGSECT"> NAME MANGLING</link></para> @@ -4274,7 +4271,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MANGLEDMAP"/>mangled map (S)</term> + <term><anchor id="MANGLEDMAP">mangled map (S)</term> <listitem><para>This is for those who want to directly map UNIX file names which cannot be represented on Windows/DOS. The mangling of names is not always what is needed. In particular you may have @@ -4299,7 +4296,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MANGLEDNAMES"/>mangled names (S)</term> + <term><anchor id="MANGLEDNAMES">mangled names (S)</term> <listitem><para>This controls whether non-DOS names under UNIX should be mapped to DOS-compatible names ("mangled") and made visible, or whether non-DOS names should simply be ignored.</para> @@ -4358,7 +4355,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="MANGLINGMETHOD"/>mangling method (G)</term> + <term><anchor id="MANGLINGMETHOD">mangling method (G)</term> <listitem><para> controls the algorithm used for the generating the mangled names. Can take two different values, "hash" and "hash2". "hash" is the default and is the algorithm that has been @@ -4373,7 +4370,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="MANGLEPREFIX"/>mangle prefix (G)</term> + <term><anchor id="MANGLEPREFIX">mangle prefix (G)</term> <listitem><para> controls the number of prefix characters from the original name used when generating the mangled names. A larger value will give a weaker @@ -4385,10 +4382,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="MANGLEDSTACK"/>mangled stack (G)</term> + <term><anchor id="MANGLEDSTACK">mangled stack (G)</term> <listitem><para>This parameter controls the number of mangled names - that should be cached in the Samba server <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>.</para> + that should be cached in the Samba server <ulink url="smbd.8.html"> + smbd(8)</ulink>.</para> <para>This stack is a list of recently mangled base names (extensions are only maintained if they are longer than 3 characters @@ -4412,7 +4409,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MANGLINGCHAR"/>mangling char (S)</term> + <term><anchor id="MANGLINGCHAR">mangling char (S)</term> <listitem><para>This controls what character is used as the <emphasis>magic</emphasis> character in <link linkend="NAMEMANGLINGSECT">name mangling</link>. The default is a '~' @@ -4429,7 +4426,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAPARCHIVE"/>map archive (S)</term> + <term><anchor id="MAPARCHIVE">map archive (S)</term> <listitem><para>This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit. The DOS archive bit is set when a file has been modified since its last backup. One @@ -4449,7 +4446,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAPHIDDEN"/>map hidden (S)</term> + <term><anchor id="MAPHIDDEN">map hidden (S)</term> <listitem><para>This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.</para> @@ -4464,7 +4461,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAPSYSTEM"/>map system (S)</term> + <term><anchor id="MAPSYSTEM">map system (S)</term> <listitem><para>This controls whether DOS style system files should be mapped to the UNIX group execute bit.</para> @@ -4479,15 +4476,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAPTOGUEST"/>map to guest (G)</term> + <term><anchor id="MAPTOGUEST">map to guest (G)</term> <listitem><para>This parameter is only useful in <link linkend="SECURITY"> security</link> modes other than <parameter>security = share</parameter> - i.e. <constant>user</constant>, <constant>server</constant>, and <constant>domain</constant>.</para> <para>This parameter can take three different values, which tell - <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> what to do with user + <ulink url="smbd.8.html">smbd(8)</ulink> what to do with user login requests that don't match a valid UNIX user in some way.</para> <para>The three settings are :</para> @@ -4535,7 +4531,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXCONNECTIONS"/>max connections (S)</term> + <term><anchor id="MAXCONNECTIONS">max connections (S)</term> <listitem><para>This option allows the number of simultaneous connections to a service to be limited. If <parameter>max connections </parameter> is greater than 0 then connections will be refused if @@ -4555,7 +4551,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXDISKSIZE"/>max disk size (G)</term> + <term><anchor id="MAXDISKSIZE">max disk size (G)</term> <listitem><para>This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in @@ -4582,7 +4578,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXLOGSIZE"/>max log size (G)</term> + <term><anchor id="MAXLOGSIZE">max log size (G)</term> <listitem><para>This option (an integer in kilobytes) specifies the max size the log file should grow to. Samba periodically checks the size and if it is exceeded it will rename the file, adding @@ -4598,7 +4594,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXMUX"/>max mux (G)</term> + <term><anchor id="MAXMUX">max mux (G)</term> <listitem><para>This option controls the maximum number of outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.</para> @@ -4610,10 +4606,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXOPENFILES"/>max open files (G)</term> + <term><anchor id="MAXOPENFILES">max open files (G)</term> <listitem><para>This parameter limits the maximum number of - open files that one <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> file + open files that one <ulink url="smbd.8.html">smbd(8)</ulink> file serving process may have open for a client at any one time. The default for this parameter is set very high (10,000) as Samba uses only one bit per unopened file.</para> @@ -4629,11 +4624,11 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXPRINTJOBS"/>max print jobs (S)</term> + <term><anchor id="MAXPRINTJOBS">max print jobs (S)</term> <listitem><para>This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment. - If this number is exceeded, <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will remote "Out of Space" to the client. + If this number is exceeded, <ulink url="smbd.8.html"><command> + smbd(8)</command></ulink> will remote "Out of Space" to the client. See all <link linkend="TOTALPRINTJOBS"><parameter>total print jobs</parameter></link>. </para> @@ -4645,7 +4640,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXPROTOCOL"/>max protocol (G)</term> + <term><anchor id="MAXPROTOCOL">max protocol (G)</term> <listitem><para>The value of the parameter (a string) is the highest protocol level that will be supported by the server.</para> @@ -4683,15 +4678,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXSMBDPROCESSES"/>max smbd processes (G)</term> + <term><anchor id="MAXSMBDPROCESSES">max smbd processes (G)</term> <listitem><para>This parameter limits the maximum number of <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> processes concurrently running on a system and is intended as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections. Remember that under normal operating - conditions, each user will have an <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> associated with him or her + conditions, each user will have an <ulink url="smbd.8.html">smbd</ulink> associated with him or her to handle connections to all shares from a given host. </para> @@ -4704,9 +4698,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXTTL"/>max ttl (G)</term> - <listitem><para>This option tells <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> + <term><anchor id="MAXTTL">max ttl (G)</term> + <listitem><para>This option tells <ulink url="nmbd.8.html">nmbd(8)</ulink> what the default 'time to live' of NetBIOS names should be (in seconds) when <command>nmbd</command> is requesting a name using either a broadcast packet or from a WINS server. You should never need to @@ -4719,9 +4712,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXWINSTTL"/>max wins ttl (G)</term> - <listitem><para>This option tells <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> when acting as a WINS server (<link linkend="WINSSUPPORT"> + <term><anchor id="MAXWINSTTL">max wins ttl (G)</term> + <listitem><para>This option tells <ulink url="nmbd.8.html">nmbd(8) + </ulink> when acting as a WINS server (<link linkend="WINSSUPPORT"> <parameter>wins support = yes</parameter></link>) what the maximum 'time to live' of NetBIOS names that <command>nmbd</command> will grant will be (in seconds). You should never need to change this @@ -4737,7 +4730,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MAXXMIT"/>max xmit (G)</term> + <term><anchor id="MAXXMIT">max xmit (G)</term> <listitem><para>This option controls the maximum packet size that will be negotiated by Samba. The default is 65535, which is the maximum. In some cases you may find you get better performance @@ -4752,7 +4745,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MESSAGECOMMAND"/>message command (G)</term> + <term><anchor id="MESSAGECOMMAND">message command (G)</term> <listitem><para>This specifies what command to run when the server receives a WinPopup style message.</para> @@ -4762,13 +4755,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>An example is:</para> - <para><command>message command = csh -c 'xedit %s;rm %s' &</command> + <para><command>message command = csh -c 'xedit %s;rm %s' &</command> </para> <para>This delivers the message using <command>xedit</command>, then removes it afterwards. <emphasis>NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY</emphasis>. That's why I - have the '&' on the end. If it doesn't return immediately then + have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).</para> @@ -4813,7 +4806,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>Default: <emphasis>no message command</emphasis></para> <para>Example: <command>message command = csh -c 'xedit %s; - rm %s' &</command></para> + rm %s' &</command></para> </listitem> </varlistentry> @@ -4821,7 +4814,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MINPASSWDLENGTH"/>min passwd length (G)</term> + <term><anchor id="MINPASSWDLENGTH">min passwd length (G)</term> <listitem><para>Synonym for <link linkend="MINPASSWORDLENGTH"> <parameter>min password length</parameter></link>.</para> </listitem> @@ -4830,7 +4823,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MINPASSWORDLENGTH"/>min password length (G)</term> + <term><anchor id="MINPASSWORDLENGTH">min password length (G)</term> <listitem><para>This option sets the minimum length in characters of a plaintext password that <command>smbd</command> will accept when performing UNIX password changing.</para> @@ -4848,7 +4841,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MINPRINTSPACE"/>min print space (S)</term> + <term><anchor id="MINPRINTSPACE">min print space (S)</term> <listitem><para>This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job. It is specified in kilobytes. The default is 0, which @@ -4866,7 +4859,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MINPROTOCOL"/>min protocol (G)</term> + <term><anchor id="MINPROTOCOL">min protocol (G)</term> <listitem><para>The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support. Please refer to the <link linkend="MAXPROTOCOL"><parameter>max protocol</parameter></link> @@ -4890,9 +4883,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MINWINSTTL"/>min wins ttl (G)</term> - <listitem><para>This option tells <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> + <term><anchor id="MINWINSTTL">min wins ttl (G)</term> + <listitem><para>This option tells <ulink url="nmbd.8.html">nmbd(8)</ulink> when acting as a WINS server (<link linkend="WINSSUPPORT"><parameter> wins support = yes</parameter></link>) what the minimum 'time to live' of NetBIOS names that <command>nmbd</command> will grant will be (in @@ -4905,7 +4897,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MSDFSPROXY"/>msdfs proxy (S)</term> + <term><anchor id="MSDFSPROXY">msdfs proxy (S)</term> <listitem><para>This parameter indicates that the share is a stand-in for another CIFS share whose location is specified by the value of the parameter. When clients attempt to connect to @@ -4916,7 +4908,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' and <link linkend="HOSTMSDFS"><parameter>host msdfs</parameter></link> options to find out how to set up a Dfs root share.</para> - <para>Example: <command>msdfs proxy = \\\\otherserver\\someshare</command></para> + <para>Example: <command>msdfs proxy = \otherserver\someshare</command></para> </listitem> </varlistentry> @@ -4924,17 +4916,17 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="MSDFSROOT"/>msdfs root (S)</term> + <term><anchor id="MSDFSROOT">msdfs root (S)</term> <listitem><para>This boolean parameter is only available if Samba is configured and compiled with the <command> --with-msdfs</command> option. If set to <constant>yes</constant>, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory. Dfs links are specified in the share directory by symbolic - links of the form <filename>msdfs:serverA\\shareA,serverB\\shareB</filename> + links of the form <filename>msdfs:serverA\shareA,serverB\shareB</filename> and so on. For more information on setting up a Dfs tree - on Samba, refer to <ulink url="msdfs.html">"Hosting a Microsoft - Distributed File System tree on Samba"</ulink> document.</para> + on Samba, refer to <ulink url="msdfs_setup.html">msdfs_setup.html + </ulink>.</para> <para>See also <link linkend="HOSTMSDFS"><parameter>host msdfs </parameter></link></para> @@ -4944,7 +4936,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="NAMECACHETIMEOUT"/>name cache timeout (G)</term> + <term><anchor id="NAMECACHETIMEOUT">name cache timeout (G)</term> <listitem><para>Specifies the number of seconds it takes before entries in samba's hostname resolve cache time out. If the timeout is set to 0. the caching is disabled. @@ -4957,7 +4949,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="NAMERESOLVEORDER"/>name resolve order (G)</term> + <term><anchor id="NAMERESOLVEORDER">name resolve order (G)</term> <listitem><para>This option is used by the programs in the Samba suite to determine what naming services to use and in what order to resolve host names to IP addresses. The option takes a space @@ -5010,7 +5002,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NETBIOSALIASES"/>netbios aliases (G)</term> + <term><anchor id="NETBIOSALIASES">netbios aliases (G)</term> <listitem><para>This is a list of NetBIOS names that <ulink url="nmbd.8.html">nmbd(8)</ulink> will advertise as additional names by which the Samba server is known. This allows one machine @@ -5031,7 +5023,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NETBIOSNAME"/>netbios name (G)</term> + <term><anchor id="NETBIOSNAME">netbios name (G)</term> <listitem><para>This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component of the host's DNS name. If a machine is a browse server or @@ -5050,7 +5042,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NETBIOSSCOPE"/>netbios scope (G)</term> + <term><anchor id="NETBIOSSCOPE">netbios scope (G)</term> <listitem><para>This sets the NetBIOS scope that Samba will operate under. This should not be set unless every machine on your LAN also sets this value.</para> @@ -5059,7 +5051,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NISHOMEDIR"/>nis homedir (G)</term> + <term><anchor id="NISHOMEDIR">nis homedir (G)</term> <listitem><para>Get the home share server from a NIS map. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote @@ -5092,7 +5084,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NONUNIXACCOUNTRANGE"/>non unix account range (G)</term> + <term><anchor id="NONUNIXACCOUNTRANGE">non unix account range (G)</term> <listitem><para>The non unix account range parameter specifies the range of 'user ids' that are allocated by the various 'non unix account' passdb backends. These backends allow @@ -5116,7 +5108,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NTACLSUPPORT"/>nt acl support (S)</term> + <term><anchor id="NTACLSUPPORT">nt acl support (S)</term> <listitem><para>This boolean parameter controls whether <ulink url="smbd.8.html">smbd(8)</ulink> will attempt to map UNIX permissions into Windows NT access control lists. @@ -5130,10 +5122,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NTPIPESUPPORT"/>nt pipe support (G)</term> + <term><anchor id="NTPIPESUPPORT">nt pipe support (G)</term> <listitem><para>This boolean parameter controls whether - <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will allow Windows NT + <ulink url="smbd.8.html">smbd(8)</ulink> will allow Windows NT clients to connect to the NT SMB specific <constant>IPC$</constant> pipes. This is a developer debugging option and can be left alone.</para> @@ -5145,7 +5136,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NTSTATUSSUPPORT"/>nt status support (G)</term> + <term><anchor id="NTSTATUSSUPPORT">nt status support (G)</term> <listitem><para>This boolean parameter controls whether <ulink url="smbd.8.html">smbd(8)</ulink> will negotiate NT specific status support with Windows NT/2k/XP clients. This is a developer @@ -5162,12 +5153,11 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="NULLPASSWORDS"/>null passwords (G)</term> + <term><anchor id="NULLPASSWORDS">null passwords (G)</term> <listitem><para>Allow or disallow client access to accounts that have null passwords. </para> - <para>See also <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> + <para>See also <ulink url="smbpasswd.5.html">smbpasswd (5)</ulink>.</para> <para>Default: <command>null passwords = no</command></para> </listitem> @@ -5177,7 +5167,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="OBEYPAMRESTRICTIONS"/>obey pam restrictions (G)</term> + <term><anchor id="OBEYPAMRESTRICTIONS">obey pam restrictions (G)</term> <listitem><para>When Samba 2.2 is configured to enable PAM support (i.e. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The @@ -5198,7 +5188,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="ONLYUSER"/>only user (S)</term> + <term><anchor id="ONLYUSER">only user (S)</term> <listitem><para>This is a boolean option that controls whether connections with usernames not in the <parameter>user</parameter> list will be allowed. By default this option is disabled so that a @@ -5226,7 +5216,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="ONLYGUEST"/>only guest (S)</term> + <term><anchor id="ONLYGUEST">only guest (S)</term> <listitem><para>A synonym for <link linkend="GUESTONLY"><parameter> guest only</parameter></link>.</para> </listitem> @@ -5235,7 +5225,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="OPLOCKBREAKWAITTIME"/>oplock break wait time (G)</term> + <term><anchor id="OPLOCKBREAKWAITTIME">oplock break wait time (G)</term> <listitem><para>This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock @@ -5253,15 +5243,15 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="OPLOCKCONTENTIONLIMIT"/>oplock contention limit (S)</term> + <term><anchor id="OPLOCKCONTENTIONLIMIT">oplock contention limit (S)</term> <listitem><para>This is a <emphasis>very</emphasis> advanced <ulink url="smbd.8.html">smbd(8)</ulink> tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file.</para> - <para>In brief it specifies a number, which causes <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>not to grant an oplock even when requested - if the approximate number of clients contending for an oplock on the same file goes over this + <para>In brief it specifies a number, which causes <ulink url="smbd.8.html">smbd</ulink> not to + grant an oplock even when requested if the approximate number of + clients contending for an oplock on the same file goes over this limit. This causes <command>smbd</command> to behave in a similar way to Windows NT.</para> @@ -5277,7 +5267,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="OPLOCKS"/>oplocks (S)</term> + <term><anchor id="OPLOCKS">oplocks (S)</term> <listitem><para>This boolean option tells <command>smbd</command> whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve @@ -5305,16 +5295,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="NTLMAUTH"/>ntlm auth (G)</term> - <listitem><para>This parameter determines - whether or not <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will + <term><anchor id="NTLMAUTH">ntlm auth (G)</term> + <listitem><para>This parameter determines whether or not <ulink url="smbd.8.html">smbd</ulink> will attempt to authenticate users using the NTLM password hash. If disabled, only the lanman password hashes will be used. </para> - <para>Please note that at least this option or <command>lanman auth</command> should - be enabled in order to be able to log in. + <para>Please note that at least this option or <command>lanman auth</command> should be enabled in order to be able to log in. </para> <para>Default : <command>ntlm auth = yes</command></para> @@ -5322,11 +5309,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="OSLEVEL"/>os level (G)</term> + <term><anchor id="OSLEVEL">os level (G)</term> <listitem><para>This integer value controls what level Samba advertises itself as for browse elections. The value of this - parameter determines whether <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> + parameter determines whether <ulink url="nmbd.8.html">nmbd(8)</ulink> has a chance of becoming a local master browser for the <parameter> WORKGROUP</parameter> in the local broadcast area.</para> @@ -5346,7 +5332,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="OS2DRIVERMAP"/>os2 driver map (G)</term> + <term><anchor id="OS2DRIVERMAP">os2 driver map (G)</term> <listitem><para>The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names. The format is:</para> @@ -5359,9 +5345,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' LaserJet 5L</command>.</para> <para>The need for the file is due to the printer driver namespace - problem described in the <ulink url="printing.html">Samba + problem described in the <ulink url="printer_driver2.html">Samba Printing HOWTO</ulink>. For more details on OS/2 clients, please - refer to the OS2-Client-HOWTO containing in the Samba documentation.</para> + refer to the <ulink url="OS2-Client-HOWTO.html">OS2-Client-HOWTO + </ulink> containing in the Samba documentation.</para> <para>Default: <command>os2 driver map = <empty string> </command></para> @@ -5370,7 +5357,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PAMPASSWORDCHANGE"/>pam password change (G)</term> + <term><anchor id="PAMPASSWORDCHANGE">pam password change (G)</term> <listitem><para>With the addition of better PAM support in Samba 2.2, this parameter, it is possible to use PAM's password change control flag for Samba. If enabled, then PAM will be used for password @@ -5388,12 +5375,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PANICACTION"/>panic action (G)</term> + <term><anchor id="PANICACTION">panic action (G)</term> <listitem><para>This is a Samba developer option that allows a - system command to be called when either <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> or <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> crashes. This is usually used to - draw attention to the fact that a problem occurred.</para> + system command to be called when either <ulink url="smbd.8.html"> + smbd(8)</ulink> or <ulink url="nmbd.8.html">nmbd(8)</ulink> + crashes. This is usually used to draw attention to the fact that + a problem occurred.</para> <para>Default: <command>panic action = <empty string></command></para> <para>Example: <command>panic action = "/bin/sleep 90000"</command></para> @@ -5401,24 +5388,20 @@ df $1 | tail -1 | awk '{print $2" "$4}' </varlistentry> <varlistentry> - <term><anchor id="PARANOIDSERVERSECURITY"/>paranoid server security (G)</term> + <term><anchor id="PARANOIDSERVERSECURITY">paranoid server security (G)</term> <listitem><para>Some version of NT 4.x allow non-guest users with a bad passowrd. When this option is enabled, samba will not use a broken NT 4.x server as password server, but instead complain - to the logs and exit. + to the logs and exit. </para> - <para>Disabling this option prevents Samba from making - this check, which involves deliberatly attempting a - bad logon to the remote server.</para> - <para>Default: <command>paranoid server security = yes</command></para> </listitem> </varlistentry> <varlistentry> - <term><anchor id="PASSDBBACKEND"/>passdb backend (G)</term> + <term><anchor id="PASSDBBACKEND">passdb backend (G)</term> <listitem><para>This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both smbpasswd and tdbsam to be used without a recompile. Multiple backends can be specified, separated by spaces. The backends will be searched in the order they are specified. New users are always added to the first backend specified. @@ -5511,13 +5494,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PASSWDCHAT"/>passwd chat (G)</term> + <term><anchor id="PASSWDCHAT">passwd chat (G)</term> <listitem><para>This string controls the <emphasis>"chat"</emphasis> - conversation that takes places between <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and the local password changing + conversation that takes places between <ulink + url="smbd.8.html">smbd</ulink> and the local password changing program to change the user's password. The string describes a - sequence of response-receive pairs that <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> uses to determine what to send to the + sequence of response-receive pairs that <ulink url="smbd.8.html"> + smbd(8)</ulink> uses to determine what to send to the <link linkend="PASSWDPROGRAM"><parameter>passwd program</parameter> </link> and what to expect back. If the expected output is not received then the password is not changed.</para> @@ -5539,8 +5522,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>The string can contain the macro <parameter>%n</parameter> which is substituted for the new password. The chat sequence can also contain the standard - macros <constant>\\n</constant>, <constant>\\r</constant>, <constant> - \\t</constant> and <constant>\\s</constant> to give line-feed, + macros <constant>\n</constant>, <constant>\r</constant>, <constant> + \t</constant> and <constant>\s</constant> to give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces @@ -5562,10 +5545,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' <parameter>passwd chat debug</parameter></link> and <link linkend="PAMPASSWORDCHANGE"> <parameter>pam password change</parameter></link>.</para> - <para>Default: <command>passwd chat = *new*password* %n\\n - *new*password* %n\\n *changed*</command></para> - <para>Example: <command>passwd chat = "*Enter OLD password*" %o\\n - "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password + <para>Default: <command>passwd chat = *new*password* %n\n + *new*password* %n\n *changed*</command></para> + <para>Example: <command>passwd chat = "*Enter OLD password*" %o\n + "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*"</command></para> </listitem> </varlistentry> @@ -5573,12 +5556,11 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PASSWDCHATDEBUG"/>passwd chat debug (G)</term> + <term><anchor id="PASSWDCHATDEBUG">passwd chat debug (G)</term> <listitem><para>This boolean specifies if the passwd chat script parameter is run in <emphasis>debug</emphasis> mode. In this mode the strings passed to and received from the passwd chat are printed - in the <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> log with a + in the <ulink url="smbd.8.html">smbd(8)</ulink> log with a <link linkend="DEBUGLEVEL"><parameter>debug level</parameter></link> of 100. This is a dangerous option as it will allow plaintext passwords to be seen in the <command>smbd</command> log. It is available to help @@ -5601,7 +5583,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PASSWDPROGRAM"/>passwd program (G)</term> + <term><anchor id="PASSWDPROGRAM">passwd program (G)</term> <listitem><para>The name of a program that can be used to set UNIX user passwords. Any occurrences of <parameter>%u</parameter> will be replaced with the user name. The user name is checked for @@ -5639,7 +5621,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PASSWORDLEVEL"/>password level (G)</term> + <term><anchor id="PASSWORDLEVEL">password level (G)</term> <listitem><para>Some client/server combinations have difficulty with mixed-case passwords. One offending client is Windows for Workgroups, which for some reason forces passwords to upper @@ -5682,7 +5664,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PASSWORDSERVER"/>password server (G)</term> + <term><anchor id="PASSWORDSERVER">password server (G)</term> <listitem><para>By specifying the name of another SMB server (such as a WinNT box) with this option, and using <command>security = domain </command> or <command>security = server</command> you can get Samba @@ -5777,7 +5759,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PATH"/>path (S)</term> + <term><anchor id="PATH">path (S)</term> <listitem><para>This parameter specifies a directory to which the user of the service is to be given access. In the case of printable services, this is where print data will spool prior to @@ -5808,7 +5790,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PIDDIRECTORY"/>pid directory (G)</term> + <term><anchor id="PIDDIRECTORY">pid directory (G)</term> <listitem><para>This option specifies the directory where pid files will be placed. </para> @@ -5820,9 +5802,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="POSIXLOCKING"/>posix locking (S)</term> - <listitem><para>The <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> + <term><anchor id="POSIXLOCKING">posix locking (S)</term> + <listitem><para>The <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> daemon maintains an database of file locks obtained by SMB clients. The default behavior is to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are @@ -5838,7 +5819,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="POSTEXEC"/>postexec (S)</term> + <term><anchor id="POSTEXEC">postexec (S)</term> <listitem><para>This option specifies a command to be run whenever the service is disconnected. It takes the usual substitutions. The command may be run as the root on some @@ -5863,7 +5844,23 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PREEXEC"/>preexec (S)</term> + <term><anchor id="POSTSCRIPT">postscript (S)</term> + <listitem><para>This parameter forces a printer to interpret + the print files as PostScript. This is done by adding a <constant>%! + </constant> to the start of print output.</para> + + <para>This is most useful when you have lots of PCs that persist + in putting a control-D at the start of print jobs, which then + confuses your printer.</para> + + <para>Default: <command>postscript = no</command></para> + </listitem> + </varlistentry> + + + + <varlistentry> + <term><anchor id="PREEXEC">preexec (S)</term> <listitem><para>This option specifies a command to be run whenever the service is connected to. It takes the usual substitutions.</para> @@ -5872,12 +5869,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' is an example:</para> <para><command>preexec = csh -c 'echo \"Welcome to %S!\" | - /usr/local/samba/bin/smbclient -M %m -I %I' & </command></para> + /usr/local/samba/bin/smbclient -M %m -I %I' & </command></para> <para>Of course, this could get annoying after a while :-)</para> <para>See also <link linkend="PREEXECCLOSE"><parameter>preexec close - </parameter></link> and <link linkend="POSTEXEC"><parameter>postexec + </parameter</link> and <link linkend="POSTEXEC"><parameter>postexec </parameter></link>.</para> <para>Default: <emphasis>none (no command executed)</emphasis></para> @@ -5889,7 +5886,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PREEXECCLOSE"/>preexec close (S)</term> + <term><anchor id="PREEXECCLOSE">preexec close (S)</term> <listitem><para>This boolean option controls whether a non-zero return code from <link linkend="PREEXEC"><parameter>preexec </parameter></link> should close the service being connected to.</para> @@ -5900,7 +5897,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PREFERREDMASTER"/>preferred master (G)</term> + <term><anchor id="PREFERREDMASTER">preferred master (G)</term> <listitem><para>This boolean parameter controls if <ulink url="nmbd.8.html">nmbd(8)</ulink> is a preferred master browser for its workgroup.</para> @@ -5929,7 +5926,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PREFEREDMASTER"/>prefered master (G)</term> + <term><anchor id="PREFEREDMASTER">prefered master (G)</term> <listitem><para>Synonym for <link linkend="PREFERREDMASTER"><parameter> preferred master</parameter></link> for people who cannot spell :-).</para> </listitem> @@ -5938,7 +5935,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRELOAD"/>preload (G)</term> + <term><anchor id="PRELOAD">preload (G)</term> <listitem><para>This is a list of services that you want to be automatically added to the browse lists. This is most useful for homes and printers services that would otherwise not be @@ -5956,7 +5953,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRESERVECASE"/>preserve case (S)</term> + <term><anchor id="PRESERVECASE">preserve case (S)</term> <listitem><para> This controls if new filenames are created with the case that the client passes, or if they are forced to be the <link linkend="DEFAULTCASE"><parameter>default case @@ -5972,7 +5969,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRINTCOMMAND"/>print command (S)</term> + <term><anchor id="PRINTCOMMAND">print command (S)</term> <listitem><para>After a print job has finished spooling to a service, this command will be used via a <command>system()</command> call to process the spool file. Typically the command specified will @@ -6062,7 +6059,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRINTOK"/>print ok (S)</term> + <term><anchor id="PRINTOK">print ok (S)</term> <listitem><para>Synonym for <link linkend="PRINTABLE"> <parameter>printable</parameter></link>.</para> </listitem> @@ -6072,7 +6069,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRINTABLE"/>printable (S)</term> + <term><anchor id="PRINTABLE">printable (S)</term> <listitem><para>If this parameter is <constant>yes</constant>, then clients may open, write to and submit spool files on the directory specified for the service. </para> @@ -6090,7 +6087,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRINTCAP"/>printcap (G)</term> + <term><anchor id="PRINTCAP">printcap (G)</term> <listitem><para>Synonym for <link linkend="PRINTCAPNAME"><parameter> printcap name</parameter></link>.</para> </listitem> @@ -6100,7 +6097,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' <varlistentry> - <term><anchor id="PRINTCAPNAME"/>printcap name (G)</term> + <term><anchor id="PRINTCAPNAME">printcap name (G)</term> <listitem><para>This parameter may be used to override the compiled-in default printcap name used by the server (usually <filename> /etc/printcap</filename>). See the discussion of the <link @@ -6126,13 +6123,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' <para>A minimal printcap file would look something like this:</para> -<para><programlisting> -print1|My Printer 1 -print2|My Printer 2 -print3|My Printer 3 -print4|My Printer 4 -print5|My Printer 5 -</programlisting></para> + <para><programlisting> + print1|My Printer 1 + print2|My Printer 2 + print3|My Printer 3 + print4|My Printer 4 + print5|My Printer 5 + </programlisting></para> <para>where the '|' separates aliases of a printer. The fact that the second alias has a space in it gives a hint to Samba @@ -6153,7 +6150,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="PRINTERADMIN"/>printer admin (S)</term> + <term><anchor id="PRINTERADMIN">printer admin (S)</term> <listitem><para>This is a list of users that can do anything to printers via the remote administration interfaces offered by MS-RPC (usually using a NT workstation). Note that the root user always @@ -6167,8 +6164,113 @@ print5|My Printer 5 + + + <varlistentry> + <term><anchor id="PRINTERDRIVER">printer driver (S)</term> + <listitem><para><emphasis>Note :</emphasis>This is a deprecated + parameter and will be removed in the next major release + following version 2.2. Please see the instructions in + the <ulink url="printer_driver2.html">Samba 2.2. Printing + HOWTO</ulink> for more information + on the new method of loading printer drivers onto a Samba server. + </para> + + <para>This option allows you to control the string + that clients receive when they ask the server for the printer driver + associated with a printer. If you are using Windows95 or Windows NT + then you can use this to automate the setup of printers on your + system.</para> + + <para>You need to set this parameter to the exact string (case + sensitive) that describes the appropriate printer driver for your + system. If you don't know the exact string to use then you should + first try with no <link linkend="PRINTERDRIVER"><parameter> + printer driver</parameter></link> option set and the client will + give you a list of printer drivers. The appropriate strings are + shown in a scroll box after you have chosen the printer manufacturer.</para> + + <para>See also <link linkend="PRINTERDRIVERFILE"><parameter>printer + driver file</parameter></link>.</para> + + <para>Example: <command>printer driver = HP LaserJet 4L</command></para> + </listitem> + </varlistentry> + + + <varlistentry> - <term><anchor id="PRINTERNAME"/>printer name (S)</term> + <term><anchor id="PRINTERDRIVERFILE">printer driver file (G)</term> + <listitem><para><emphasis>Note :</emphasis>This is a deprecated + parameter and will be removed in the next major release + following version 2.2. Please see the instructions in + the <ulink url="printer_driver2.html">Samba 2.2. Printing + HOWTO</ulink> for more information + on the new method of loading printer drivers onto a Samba server. + </para> + + <para>This parameter tells Samba where the printer driver + definition file, used when serving drivers to Windows 95 clients, is + to be found. If this is not set, the default is :</para> + + <para><filename><replaceable>SAMBA_INSTALL_DIRECTORY</replaceable> + /lib/printers.def</filename></para> + + <para>This file is created from Windows 95 <filename>msprint.inf + </filename> files found on the Windows 95 client system. For more + details on setting up serving of printer drivers to Windows 95 + clients, see the outdated documentation file in the <filename>docs/</filename> + directory, <filename>PRINTER_DRIVER.txt</filename>.</para> + + <para>See also <link linkend="PRINTERDRIVERLOCATION"><parameter> + printer driver location</parameter></link>.</para> + + <para>Default: <emphasis>None (set in compile).</emphasis></para> + + <para>Example: <command>printer driver file = + /usr/local/samba/printers/drivers.def</command></para> + </listitem> + </varlistentry> + + + + + <varlistentry> + <term><anchor id="PRINTERDRIVERLOCATION">printer driver location (S)</term> + <listitem><para><emphasis>Note :</emphasis>This is a deprecated + parameter and will be removed in the next major release + following version 2.2. Please see the instructions in + the <ulink url="printer_driver2.html">Samba 2.2. Printing + HOWTO</ulink> for more information + on the new method of loading printer drivers onto a Samba server. + </para> + + <para>This parameter tells clients of a particular printer + share where to find the printer driver files for the automatic + installation of drivers for Windows 95 machines. If Samba is set up + to serve printer drivers to Windows 95 machines, this should be set to</para> + + <para><command>\\MACHINE\PRINTER$</command></para> + + <para>Where MACHINE is the NetBIOS name of your Samba server, + and PRINTER$ is a share you set up for serving printer driver + files. For more details on setting this up see the outdated documentation + file in the <filename>docs/</filename> directory, <filename> + PRINTER_DRIVER.txt</filename>.</para> + + <para>See also <link linkend="PRINTERDRIVERFILE"><parameter> + printer driver file</parameter></link>.</para> + + <para>Default: <command>none</command></para> + <para>Example: <command>printer driver location = \\MACHINE\PRINTER$ + </command></para> + </listitem> + </varlistentry> + + + + <varlistentry> + <term><anchor id="PRINTERNAME">printer name (S)</term> <listitem><para>This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent.</para> @@ -6185,7 +6287,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="PRINTER"/>printer (S)</term> + <term><anchor id="PRINTER">printer (S)</term> <listitem><para>Synonym for <link linkend="PRINTERNAME"><parameter> printer name</parameter></link>.</para> </listitem> @@ -6194,7 +6296,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="PRINTING"/>printing (S)</term> + <term><anchor id="PRINTING">printing (S)</term> <listitem><para>This parameters controls how printer status information is interpreted on your system. It also affects the default values for the <parameter>print command</parameter>, @@ -6225,7 +6327,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="PRIVATEDIR"/>private dir (G)</term> + <term><anchor id="PRIVATEDIR">private dir (G)</term> <listitem><para>This parameters defines the directory smbd will use for storing such files as <filename>smbpasswd</filename> and <filename>secrets.tdb</filename>. @@ -6239,7 +6341,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="PROTOCOL"/>protocol (G)</term> + <term><anchor id="PROTOCOL">protocol (G)</term> <listitem><para>Synonym for <link linkend="MAXPROTOCOL"> <parameter>max protocol</parameter></link>.</para></listitem> </varlistentry> @@ -6248,7 +6350,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="PUBLIC"/>public (S)</term> + <term><anchor id="PUBLIC">public (S)</term> <listitem><para>Synonym for <link linkend="GUESTOK"><parameter>guest ok</parameter></link>.</para> </listitem> @@ -6257,7 +6359,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="QUEUEPAUSECOMMAND"/>queuepause command (S)</term> + <term><anchor id="QUEUEPAUSECOMMAND">queuepause command (S)</term> <listitem><para>This parameter specifies the command to be executed on the server host in order to pause the printer queue.</para> @@ -6286,7 +6388,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="QUEUERESUMECOMMAND"/>queueresume command (S)</term> + <term><anchor id="QUEUERESUMECOMMAND">queueresume command (S)</term> <listitem><para>This parameter specifies the command to be executed on the server host in order to resume the printer queue. It is the command to undo the behavior that is caused by the @@ -6321,7 +6423,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="READBMPX"/>read bmpx (G)</term> + <term><anchor id="READBMPX">read bmpx (G)</term> <listitem><para>This boolean parameter controls whether <ulink url="smbd.8.html">smbd(8)</ulink> will support the "Read Block Multiplex" SMB. This is now rarely used and defaults to @@ -6336,7 +6438,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="READLIST"/>read list (S)</term> + <term><anchor id="READLIST">read list (S)</term> <listitem><para>This is a list of users that are given read-only access to a service. If the connecting user is in this list then they will not be given write access, no matter what the <link @@ -6358,7 +6460,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="READONLY"/>read only (S)</term> + <term><anchor id="READONLY">read only (S)</term> <listitem><para>An inverted synonym is <link linkend="WRITEABLE"> <parameter>writeable</parameter></link>.</para> @@ -6377,7 +6479,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="READRAW"/>read raw (G)</term> + <term><anchor id="READRAW">read raw (G)</term> <listitem><para>This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients.</para> @@ -6400,7 +6502,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="READSIZE"/>read size (G)</term> + <term><anchor id="READSIZE">read size (G)</term> <listitem><para>The option <parameter>read size</parameter> affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB @@ -6427,7 +6529,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="REALM"/>realm (G)</term> + <term><anchor id="REALM">realm (G)</term> <listitem><para> This option specifies the kerberos realm to use. The realm is used as the ADS equivalent of the NT4<command>domain</command>. It @@ -6440,7 +6542,7 @@ print5|My Printer 5 </varlistentry> <varlistentry> - <term><anchor id="REMOTEANNOUNCE"/>remote announce (G)</term> + <term><anchor id="REMOTEANNOUNCE">remote announce (G)</term> <listitem><para>This option allows you to setup <ulink url="nmbd.8.html">nmbd(8)</ulink> to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name.</para> @@ -6465,7 +6567,7 @@ print5|My Printer 5 addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable.</para> - <para>See the documentation file <ulink url="improved-browsing.html">BROWSING</ulink> + <para>See the documentation file <filename>BROWSING.txt</filename> in the <filename>docs/</filename> directory.</para> <para>Default: <command>remote announce = <empty string> @@ -6476,7 +6578,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="REMOTEBROWSESYNC"/>remote browse sync (G)</term> + <term><anchor id="REMOTEBROWSESYNC">remote browse sync (G)</term> <listitem><para>This option allows you to setup <ulink url="nmbd.8.html">nmbd(8)</ulink> to periodically request synchronization of browse lists with the master browser of a Samba @@ -6514,7 +6616,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="RESTRICTANONYMOUS"/>restrict anonymous (G)</term> + <term><anchor id="RESTRICTANONYMOUS">restrict anonymous (G)</term> <listitem><para>This is a integer parameter, and mirrors as much as possible the functinality the <constant>RestrictAnonymous</constant> @@ -6527,7 +6629,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="ROOT"/>root (G)</term> + <term><anchor id="ROOT">root (G)</term> <listitem><para>Synonym for <link linkend="ROOTDIRECTORY"> <parameter>root directory"</parameter></link>.</para> </listitem> @@ -6536,7 +6638,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="ROOTDIR"/>root dir (G)</term> + <term><anchor id="ROOTDIR">root dir (G)</term> <listitem><para>Synonym for <link linkend="ROOTDIRECTORY"> <parameter>root directory"</parameter></link>.</para> </listitem> @@ -6544,7 +6646,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="ROOTDIRECTORY"/>root directory (G)</term> + <term><anchor id="ROOTDIRECTORY">root directory (G)</term> <listitem><para>The server will <command>chroot()</command> (i.e. Change its root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the @@ -6576,7 +6678,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="ROOTPOSTEXEC"/>root postexec (S)</term> + <term><anchor id="ROOTPOSTEXEC">root postexec (S)</term> <listitem><para>This is the same as the <parameter>postexec</parameter> parameter except that the command is run as root. This is useful for unmounting filesystems @@ -6591,7 +6693,7 @@ print5|My Printer 5 </varlistentry> <varlistentry> - <term><anchor id="ROOTPREEXEC"/>root preexec (S)</term> + <term><anchor id="ROOTPREEXEC">root preexec (S)</term> <listitem><para>This is the same as the <parameter>preexec</parameter> parameter except that the command is run as root. This is useful for mounting filesystems (such as CDROMs) when a @@ -6609,7 +6711,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="ROOTPREEXECCLOSE"/>root preexec close (S)</term> + <term><anchor id="ROOTPREEXECCLOSE">root preexec close (S)</term> <listitem><para>This is the same as the <parameter>preexec close </parameter> parameter except that the command is run as root.</para> @@ -6623,14 +6725,14 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SECURITY"/>security (G)</term> + <term><anchor id="SECURITY">security (G)</term> <listitem><para>This option affects how clients respond to Samba and is one of the most important settings in the <filename> smb.conf</filename> file.</para> <para>The option sets the "security mode bit" in replies to - protocol negotiations with <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to turn share level security on or off. Clients decide + protocol negotiations with <ulink url="smbd.8.html">smbd(8) + </ulink> to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.</para> @@ -6675,7 +6777,7 @@ print5|My Printer 5 <para>The different settings will now be explained.</para> - <para><anchor id="SECURITYEQUALSSHARE"/><emphasis>SECURITY = SHARE + <para><anchor id="SECURITYEQUALSSHARE"><emphasis>SECURITY = SHARE </emphasis></para> <para>When clients connect to a share level security server they @@ -6744,10 +6846,10 @@ print5|My Printer 5 <para>See also the section <link linkend="VALIDATIONSECT"> NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para> - <para><anchor id="SECURITYEQUALSUSER"/><emphasis>SECURITY = USER + <para><anchor id="SECURITYEQUALSUSER"><emphasis>SECURITY = USER </emphasis></para> - <para>This is the default security setting in Samba 3.0. + <para>This is the default security setting in Samba 2.2. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the <link linkend="USERNAMEMAP"><parameter>username map</parameter></link> @@ -6771,27 +6873,24 @@ print5|My Printer 5 <para>See also the section <link linkend="VALIDATIONSECT"> NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para> - <para><anchor id="SECURITYEQUALSDOMAIN"/><emphasis>SECURITY = DOMAIN - + <para><anchor id="SECURITYEQUALSSERVER"><emphasis>SECURITY = SERVER </emphasis></para> - <para>This mode will only work correctly if <citerefentry><refentrytitle>net</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> has been used to add this - machine into a Windows NT Domain. It expects the <link - linkend="ENCRYPTPASSWORDS"><parameter>encrypted passwords</parameter> - </link> parameter to be set to <constant>yes</constant>. In this - mode Samba will try to validate the username/password by passing - it to a Windows NT Primary or Backup Domain Controller, in exactly - the same way that a Windows NT Server would do.</para> - - <para><emphasis>Note</emphasis> that a valid UNIX user must still - exist as well as the account on the Domain Controller to allow - Samba to have a valid UNIX account to map file access to.</para> + <para>In this mode Samba will try to validate the username/password + by passing it to another SMB server, such as an NT box. If this + fails it will revert to <command>security = user</command>, but note + that if encrypted passwords have been negotiated then Samba cannot + revert back to checking the UNIX password file, it must have a valid + <filename>smbpasswd</filename> file to check users against. See the + documentation file in the <filename>docs/</filename> directory + <filename>ENCRYPTION.txt</filename> for details on how to set this + up.</para> - <para><emphasis>Note</emphasis> that from the client's point - of view <command>security = domain</command> is the same as <command>security = user - </command>. It only affects how the server deals with the authentication, - it does not in any way affect what the client sees.</para> + <para><emphasis>Note</emphasis> that from the client's point of + view <command>security = server</command> is the same as <command> + security = user</command>. It only affects how the server deals + with the authentication, it does not in any way affect what the + client sees.</para> <para><emphasis>Note</emphasis> that the name of the resource being requested is <emphasis>not</emphasis> sent to the server until after @@ -6809,42 +6908,27 @@ print5|My Printer 5 server</parameter></link> parameter and the <link linkend="ENCRYPTPASSWORDS"><parameter>encrypted passwords</parameter> </link> parameter.</para> - - <para><anchor id="SECURITYEQUALSSERVER"/><emphasis>SECURITY = SERVER + + <para><anchor id="SECURITYEQUALSDOMAIN"><emphasis>SECURITY = DOMAIN </emphasis></para> - <para>In this mode Samba will try to validate the username/password - by passing it to another SMB server, such as an NT box. If this - fails it will revert to <command>security = - user</command>. It expects the <link + <para>This mode will only work correctly if <ulink + url="smbpasswd.8.html">smbpasswd(8)</ulink> has been used to add this + machine into a Windows NT Domain. It expects the <link linkend="ENCRYPTPASSWORDS"><parameter>encrypted passwords</parameter> - </link> parameter to be set to - <constant>yes</constant>, unless the remote server - does not support them. However note - that if encrypted passwords have been negotiated then Samba cannot - revert back to checking the UNIX password file, it must have a valid - <filename>smbpasswd</filename> file to check users against. See the - documentation file in the <filename>docs/</filename> directory - <filename>ENCRYPTION.txt</filename> for details on how to set this - up.</para> + </link> parameter to be set to <constant>yes</constant>. In this + mode Samba will try to validate the username/password by passing + it to a Windows NT Primary or Backup Domain Controller, in exactly + the same way that a Windows NT Server would do.</para> - <para><emphasis>Note</emphasis> this mode of operation - has significant pitfalls, due to the fact that is - activly initiates a man-in-the-middle attack on the - remote SMB server. In particular, this mode of - operation can cause significant resource consuption on - the PDC, as it must maintain an active connection for - the duration of the user's session. Furthermore, if - this connection is lost, there is no way to - reestablish it, and futher authenticaions to the Samba - server may fail. (From a single client, till it - disconnects). </para> + <para><emphasis>Note</emphasis> that a valid UNIX user must still + exist as well as the account on the Domain Controller to allow + Samba to have a valid UNIX account to map file access to.</para> - <para><emphasis>Note</emphasis> that from the client's point of - view <command>security = server</command> is the same as <command> - security = user</command>. It only affects how the server deals - with the authentication, it does not in any way affect what the - client sees.</para> + <para><emphasis>Note</emphasis> that from the client's point + of view <command>security = domain</command> is the same as <command>security = user + </command>. It only affects how the server deals with the authentication, + it does not in any way affect what the client sees.</para> <para><emphasis>Note</emphasis> that the name of the resource being requested is <emphasis>not</emphasis> sent to the server until after @@ -6855,6 +6939,14 @@ print5|My Printer 5 See the <link linkend="MAPTOGUEST"><parameter>map to guest</parameter> </link> parameter for details on doing this.</para> + <para><emphasis>BUG:</emphasis> There is currently a bug in the + implementation of <command>security = domain</command> with respect + to multi-byte character set usernames. The communication with a + Domain Controller must be done in UNICODE and Samba currently + does not widen multi-byte user names to UNICODE correctly, thus + a multi-byte username will not be recognized correctly at the + Domain Controller. This issue will be addressed in a future release.</para> + <para>See also the section <link linkend="VALIDATIONSECT"> NOTE ABOUT USERNAME/PASSWORD VALIDATION</link>.</para> @@ -6862,17 +6954,16 @@ print5|My Printer 5 server</parameter></link> parameter and the <link linkend="ENCRYPTPASSWORDS"><parameter>encrypted passwords</parameter> </link> parameter.</para> - + <para>Default: <command>security = USER</command></para> <para>Example: <command>security = DOMAIN</command></para> - </listitem> </varlistentry> <varlistentry> - <term><anchor id="SECURITYMASK"/>security mask (S)</term> + <term><anchor id="SECURITYMASK">security mask (S)</term> <listitem><para>This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security @@ -6907,7 +6998,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SERVERSTRING"/>server string (G)</term> + <term><anchor id="SERVERSTRING">server string (G)</term> <listitem><para>This controls what string will show up in the printer comment box in print manager and next to the IPC connection in <command>net view</command>. It can be any string that you wish @@ -6932,7 +7023,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SETDIRECTORY"/>set directory (S)</term> + <term><anchor id="SETDIRECTORY">set directory (S)</term> <listitem><para>If <command>set directory = no</command>, then users of the service may not use the setdir command to change directory.</para> @@ -6948,7 +7039,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SHAREMODES"/>share modes (S)</term> + <term><anchor id="SHAREMODES">share modes (S)</term> <listitem><para>This enables or disables the honoring of the <parameter>share modes</parameter> during a file open. These modes are used by clients to gain exclusive read or write access @@ -6977,7 +7068,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SHORTPRESERVECASE"/>short preserve case (S)</term> + <term><anchor id="SHORTPRESERVECASE">short preserve case (S)</term> <listitem><para>This boolean parameter controls if new files which conform to 8.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced @@ -6997,7 +7088,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SHOWADDPRINTERWIZARD"/>show add printer wizard (G)</term> + <term><anchor id="SHOWADDPRINTERWIZARD">show add printer wizard (G)</term> <listitem><para>With the introduction of MS-RPC based printing support for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will appear on Samba hosts in the share listing. Normally this folder will @@ -7032,7 +7123,7 @@ print5|My Printer 5 <varlistentry> - <term><anchor id="SHUTDOWNSCRIPT"/>shutdown script (G)</term> + <term><anchor id="SHUTDOWNSCRIPT">shutdown script (G)</term> <listitem><para><emphasis>This parameter only exists in the HEAD cvs branch</emphasis> This a full path name to a script called by <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> that @@ -7058,15 +7149,15 @@ print5|My Printer 5 <para>Default: <emphasis>None</emphasis>.</para> <para>Example: <command>abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</command></para> <para>Shutdown script example: -<programlisting> -#!/bin/bash + <programlisting> + #!/bin/bash -$time=0 -let "time/60" -let "time++" + $time=0 + let "time/60" + let "time++" -/sbin/shutdown $3 $4 +$time $1 & -</programlisting> + /sbin/shutdown $3 $4 +$time $1 & + </programlisting> Shutdown does not return so we need to launch it in background. </para> @@ -7076,7 +7167,7 @@ let "time++" <varlistentry> - <term><anchor id="SMBPASSWDFILE"/>smb passwd file (G)</term> + <term><anchor id="SMBPASSWDFILE">smb passwd file (G)</term> <listitem><para>This option sets the path to the encrypted smbpasswd file. By default the path to the smbpasswd file is compiled into Samba.</para> @@ -7091,7 +7182,7 @@ let "time++" <varlistentry> - <term><anchor id="SMBPORTS"/>smb ports (G)</term> + <term><anchor id="SMBPORTS">smb ports (G)</term> <listitem><para>Specifies which ports the server should listen on for SMB traffic. </para> @@ -7102,7 +7193,7 @@ let "time++" </varlistentry> <varlistentry> - <term><anchor id="SOCKETADDRESS"/>socket address (G)</term> + <term><anchor id="SOCKETADDRESS">socket address (G)</term> <listitem><para>This option allows you to control what address Samba will listen for connections on. This is used to support multiple virtual interfaces on the one server, each @@ -7119,7 +7210,7 @@ let "time++" <varlistentry> - <term><anchor id="SOCKETOPTIONS"/>socket options (G)</term> + <term><anchor id="SOCKETOPTIONS">socket options (G)</term> <listitem><para>This option allows you to set socket options to be used when talking with the client.</para> @@ -7192,7 +7283,7 @@ let "time++" <varlistentry> - <term><anchor id="SOURCEENVIRONMENT"/>source environment (G)</term> + <term><anchor id="SOURCEENVIRONMENT">source environment (G)</term> <listitem><para>This parameter causes Samba to set environment variables as per the content of the file named.</para> @@ -7214,23 +7305,17 @@ let "time++" /usr/local/smb_env_vars</command></para> </listitem> </varlistentry> +<varlistentry> +<term><anchor id="SPNEGO">use spnego (G)</term> +<listitem><para> This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. As of samba 3.0alpha it must be set to "no" for these clients to join a samba domain controller. It can be set to "yes" to allow samba to participate in an AD domain controlled by a Windows2000 domain controller.</para> +<para>Default: <emphasis>use spnego = yes</emphasis></para> +</listitem> +</varlistentry> <varlistentry> - <term><anchor id="SPNEGO"/>use spnego (G)</term> - <listitem><para> This variable controls controls whether samba will try - to use Simple and Protected NEGOciation (as specified by rfc2478) with - WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. - Unless further issues are discovered with our SPNEGO - implementation, there is no reason this should ever be - disabled.</para> - <para>Default: <emphasis>use spnego = yes</emphasis></para> - </listitem> - </varlistentry> - - <varlistentry> - <term><anchor id="STATCACHE"/>stat cache (G)</term> - <listitem><para>This parameter determines if <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will use a cache in order to + <term><anchor id="STATCACHE">stat cache (G)</term> + <listitem><para>This parameter determines if <ulink + url="smbd.8.html">smbd(8)</ulink> will use a cache in order to speed up case insensitive name mappings. You should never need to change this parameter.</para> @@ -7239,7 +7324,7 @@ let "time++" </varlistentry> <varlistentry> - <term><anchor id="STATCACHESIZE"/>stat cache size (G)</term> + <term><anchor id="STATCACHESIZE">stat cache size (G)</term> <listitem><para>This parameter determines the number of entries in the <parameter>stat cache</parameter>. You should never need to change this parameter.</para> @@ -7251,7 +7336,7 @@ let "time++" <varlistentry> - <term><anchor id="STRICTALLOCATE"/>strict allocate (S)</term> + <term><anchor id="STRICTALLOCATE">strict allocate (S)</term> <listitem><para>This is a boolean that controls the handling of disk space allocation in the server. When this is set to <constant>yes</constant> the server will change from UNIX behaviour of not committing real @@ -7275,7 +7360,7 @@ let "time++" <varlistentry> - <term><anchor id="STRICTLOCKING"/>strict locking (S)</term> + <term><anchor id="STRICTLOCKING">strict locking (S)</term> <listitem><para>This is a boolean that controls the handling of file locking in the server. When this is set to <constant>yes</constant> the server will check every read and write access for file locks, and @@ -7295,7 +7380,7 @@ let "time++" <varlistentry> - <term><anchor id="STRICTSYNC"/>strict sync (S)</term> + <term><anchor id="STRICTSYNC">strict sync (S)</term> <listitem><para>Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk. Under UNIX, a sync call forces @@ -7303,8 +7388,7 @@ let "time++" all outstanding data in kernel disk buffers has been safely stored onto stable storage. This is very slow and should only be done rarely. Setting this parameter to <constant>no</constant> (the - default) means that <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> ignores the Windows applications requests for + default) means that <ulink url="smbd.8.html">smbd</ulink> ignores the Windows applications requests for a sync call. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting. In addition, this fixes many @@ -7320,7 +7404,7 @@ let "time++" <varlistentry> - <term><anchor id="STRIPDOT"/>strip dot (G)</term> + <term><anchor id="STRIPDOT">strip dot (G)</term> <listitem><para>This is a boolean that controls whether to strip trailing dots off UNIX filenames. This helps with some CDROMs that have filenames ending in a single dot.</para> @@ -7332,7 +7416,7 @@ let "time++" <varlistentry> - <term><anchor id="SYNCALWAYS"/>sync always (S)</term> + <term><anchor id="SYNCALWAYS">sync always (S)</term> <listitem><para>This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns. If this is <constant>no</constant> then the server will be @@ -7354,7 +7438,7 @@ let "time++" <varlistentry> - <term><anchor id="SYSLOG"/>syslog (G)</term> + <term><anchor id="SYSLOG">syslog (G)</term> <listitem><para>This parameter maps how Samba debug messages are logged onto the system syslog logging levels. Samba debug level zero maps onto syslog <constant>LOG_ERR</constant>, debug @@ -7374,7 +7458,7 @@ let "time++" <varlistentry> - <term><anchor id="SYSLOGONLY"/>syslog only (G)</term> + <term><anchor id="SYSLOGONLY">syslog only (G)</term> <listitem><para>If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files.</para> @@ -7386,7 +7470,7 @@ let "time++" <varlistentry> - <term><anchor id="TEMPLATEHOMEDIR"/>template homedir (G)</term> + <term><anchor id="TEMPLATEHOMEDIR">template homedir (G)</term> <listitem><para>When filling out the user information for a Windows NT user, the <ulink url="winbindd.8.html">winbindd(8)</ulink> daemon uses this parameter to fill in the home directory for that user. @@ -7402,10 +7486,9 @@ let "time++" <varlistentry> - <term><anchor id="TEMPLATESHELL"/>template shell (G)</term> + <term><anchor id="TEMPLATESHELL">template shell (G)</term> <listitem><para>When filling out the user information for a Windows NT - user, the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon + user, the <ulink url="winbindd.8.html">winbindd(8)</ulink> daemon uses this parameter to fill in the login shell for that user.</para> <para>Default: <command>template shell = /bin/false</command></para> @@ -7415,7 +7498,7 @@ let "time++" <varlistentry> - <term><anchor id="TIMEOFFSET"/>time offset (G)</term> + <term><anchor id="TIMEOFFSET">time offset (G)</term> <listitem><para>This parameter is a setting in minutes to add to the normal GMT to local time conversion. This is useful if you are serving a lot of PCs that have incorrect daylight @@ -7429,9 +7512,9 @@ let "time++" <varlistentry> - <term><anchor id="TIMESERVER"/>time server (G)</term> - <listitem><para>This parameter determines if <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> advertises itself as a time server to Windows + <term><anchor id="TIMESERVER">time server (G)</term> + <listitem><para>This parameter determines if <ulink url="nmbd.8.html"> + nmbd(8)</ulink> advertises itself as a time server to Windows clients.</para> <para>Default: <command>time server = no</command></para> @@ -7440,7 +7523,7 @@ let "time++" <varlistentry> - <term><anchor id="TIMESTAMPLOGS"/>timestamp logs (G)</term> + <term><anchor id="TIMESTAMPLOGS">timestamp logs (G)</term> <listitem><para>Synonym for <link linkend="DEBUGTIMESTAMP"><parameter> debug timestamp</parameter></link>.</para> </listitem> @@ -7451,17 +7534,16 @@ let "time++" <varlistentry> - <term><anchor id="TOTALPRINTJOBS"/>total print jobs (G)</term> + <term><anchor id="TOTALPRINTJOBS">total print jobs (G)</term> <listitem><para>This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time. If a print job is submitted - by a client which will exceed this number, then <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> will return an + by a client which will exceed this number, then <ulink url="smbd.8.html">smbd</ulink> will return an error indicating that no space is available on the server. The default value of 0 means that no such limit exists. This parameter can be used to prevent a server from exceeding its capacity and is designed as a printing throttle. See also - <link linkend="MAXPRINTJOBS"><parameter>max print jobs</parameter></link>. + <link linkend="MAXPRINTJOBS"><parameter>max print jobs</parameter</link>. </para> <para>Default: <command>total print jobs = 0</command></para> @@ -7470,7 +7552,7 @@ let "time++" </varlistentry> <varlistentry> - <term><anchor id="UNICODE"/>unicode (G)</term> + <term><anchor id="UNICODE">unicode (G)</term> <listitem><para>Specifies whether Samba should try to use unicode on the wire by default. Note: This does NOT mean that samba will assume that the unix machine uses unicode! @@ -7482,19 +7564,19 @@ let "time++" </varlistentry> <varlistentry> - <term><anchor id="UNIXCHARSET"/>unix charset (G)</term> + <term><anchor id="UNIXCHARSET">unix charset (G)</term> <listitem><para>Specifies the charset the unix machine Samba runs on uses. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use. </para> - <para>Default: <command>unix charset = UTF8</command></para> - <para>Example: <command>unix charset = ASCII</command></para> + <para>Default: <command>unix charset = ASCII</command></para> + <para>Example: <command>unix charset = UTF8</command></para> </listitem> </varlistentry> <varlistentry> - <term><anchor id="UNIXEXTENSIONS"/>unix extensions(G)</term> + <term><anchor id="UNIXEXTENSIONS">unix extensions(G)</term> <listitem><para>This boolean parameter controls whether Samba implments the CIFS UNIX extensions, as defined by HP. These extensions enable Samba to better serve UNIX CIFS clients @@ -7510,7 +7592,7 @@ let "time++" <varlistentry> - <term><anchor id="UNIXPASSWORDSYNC"/>unix password sync (G)</term> + <term><anchor id="UNIXPASSWORDSYNC">unix password sync (G)</term> <listitem><para>This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. @@ -7531,7 +7613,7 @@ let "time++" <varlistentry> - <term><anchor id="UPDATEENCRYPTED"/>update encrypted (G)</term> + <term><anchor id="UPDATEENCRYPTED">update encrypted (G)</term> <listitem><para>This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as @@ -7562,7 +7644,7 @@ let "time++" <varlistentry> - <term><anchor id="USECLIENTDRIVER"/>use client driver (S)</term> + <term><anchor id="USECLIENTDRIVER">use client driver (S)</term> <listitem><para>This parameter applies only to Windows NT/2000 clients. It has no affect on Windows 95/98/ME clients. When serving a printer to Windows NT/2000 clients without first installing @@ -7600,7 +7682,7 @@ let "time++" <varlistentry> - <term><anchor id="USEMMAP"/>use mmap (G)</term> + <term><anchor id="USEMMAP">use mmap (G)</term> <listitem><para>This global parameter determines if the tdb internals of Samba can depend on mmap working correctly on the running system. Samba requires a coherent mmap/read-write system memory cache. Currently only HPUX does not have such a @@ -7618,7 +7700,27 @@ let "time++" <varlistentry> - <term><anchor id="USER"/>user (S)</term> + <term><anchor id="USERHOSTS">use rhosts (G)</term> + <listitem><para>If this global parameter is <constant>yes</constant>, it specifies + that the UNIX user's <filename>.rhosts</filename> file in their home directory + will be read to find the names of hosts and users who will be allowed + access without specifying a password.</para> + + <para><emphasis>NOTE:</emphasis> The use of <parameter>use rhosts + </parameter> can be a major security hole. This is because you are + trusting the PC to supply the correct username. It is very easy to + get a PC to supply a false username. I recommend that the <parameter> + use rhosts</parameter> option be only used if you really know what + you are doing.</para> + + <para>Default: <command>use rhosts = no</command></para> + </listitem> + </varlistentry> + + + + <varlistentry> + <term><anchor id="USER">user (S)</term> <listitem><para>Synonym for <link linkend="USERNAME"><parameter> username</parameter></link>.</para> </listitem> @@ -7627,7 +7729,7 @@ let "time++" <varlistentry> - <term><anchor id="USERS"/>users (S)</term> + <term><anchor id="USERS">users (S)</term> <listitem><para>Synonym for <link linkend="USERNAME"><parameter> username</parameter></link>.</para> </listitem> @@ -7635,7 +7737,7 @@ let "time++" <varlistentry> - <term><anchor id="USERNAME"/>username (S)</term> + <term><anchor id="USERNAME">username (S)</term> <listitem><para>Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right).</para> @@ -7676,7 +7778,7 @@ let "time++" will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name.</para> - <para>If any of the usernames begin with a '&' then the name + <para>If any of the usernames begin with a '&'then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.</para> @@ -7700,7 +7802,7 @@ let "time++" <varlistentry> - <term><anchor id="USERNAMELEVEL"/>username level (G)</term> + <term><anchor id="USERNAMELEVEL">username level (G)</term> <listitem><para>This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username. By default Samba tries all lowercase, followed by the @@ -7723,7 +7825,7 @@ let "time++" <varlistentry> - <term><anchor id="USERNAMEMAP"/>username map (G)</term> + <term><anchor id="USERNAMEMAP">username map (G)</term> <listitem><para>This option allows you to specify a file containing a mapping of usernames from the clients to the server. This can be used for several purposes. The most common is to map usernames @@ -7786,10 +7888,10 @@ let "time++" '!' to tell Samba to stop processing if it gets a match on that line.</para> -<para><programlisting> -!sys = mary fred -guest = * -</programlisting></para> + <para><programlisting> + !sys = mary fred + guest = * + </programlisting></para> <para>Note that the remapping is applied to all occurrences of usernames. Thus if you connect to \\server\fred and <constant> @@ -7815,7 +7917,7 @@ guest = * <varlistentry> - <term><anchor id="USESENDFILE"/>use sendfile (S)</term> + <term><anchor id="USESENDFILE">use sendfile (S)</term> <listitem><para>If this parameter is <constant>yes</constant>, and Samba was built with the --with-sendfile-support option, and the underlying operating system supports sendfile system call, then some SMB read calls (mainly ReadAndX @@ -7832,7 +7934,7 @@ guest = * <varlistentry> - <term><anchor id="UTMP"/>utmp (G)</term> + <term><anchor id="UTMP">utmp (G)</term> <listitem><para>This boolean parameter is only available if Samba has been configured and compiled with the option <command> --with-utmp</command>. If set to <constant>yes</constant> then Samba will attempt @@ -7854,7 +7956,7 @@ guest = * </varlistentry> <varlistentry> - <term><anchor id="UTMPDIRECTORY"/>utmp directory(G)</term> + <term><anchor id="UTMPDIRECTORY">utmp directory(G)</term> <listitem><para>This parameter is only available if Samba has been configured and compiled with the option <command> --with-utmp</command>. It specifies a directory pathname that is @@ -7871,7 +7973,7 @@ guest = * </varlistentry> <varlistentry> - <term><anchor id="WTMPDIRECTORY"/>wtmp directory(G)</term> + <term><anchor id="WTMPDIRECTORY">wtmp directory(G)</term> <listitem><para>This parameter is only available if Samba has been configured and compiled with the option <command> --with-utmp</command>. It specifies a directory pathname that is @@ -7893,9 +7995,9 @@ guest = * <varlistentry> - <term><anchor id="VALIDUSERS"/>valid users (S)</term> + <term><anchor id="VALIDUSERS">valid users (S)</term> <listitem><para>This is a list of users that should be allowed - to login to this service. Names starting with '@', '+' and '&' + to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the <parameter>invalid users</parameter> parameter.</para> @@ -7920,7 +8022,7 @@ guest = * <varlistentry> - <term><anchor id="VETOFILES"/>veto files(S)</term> + <term><anchor id="VETOFILES">veto files(S)</term> <listitem><para>This is a list of files and directories that are neither visible nor accessible. Each entry in the list must be separated by a '/', which allows spaces to be included @@ -7968,7 +8070,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="VETOOPLOCKFILES"/>veto oplock files (S)</term> + <term><anchor id="VETOOPLOCKFILES">veto oplock files (S)</term> <listitem><para>This parameter is only valid when the <link linkend="OPLOCKS"><parameter>oplocks</parameter></link> parameter is turned on for a share. It allows the Samba administrator @@ -7994,7 +8096,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ </varlistentry> <varlistentry> - <term><anchor id="VFSPATH"/>vfs path (S)</term> + <term><anchor id="VFSPATH">vfs path (S)</term> <listitem><para>This parameter specifies the directory to look in for vfs modules. The name of every <command>vfs object </command> will be prepended by this directory @@ -8007,7 +8109,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ </varlistentry> <varlistentry> - <term><anchor id="VFSOBJECT"/>vfs object (S)</term> + <term><anchor id="VFSOBJECT">vfs object (S)</term> <listitem><para>This parameter specifies a shared object files that are used for Samba VFS I/O operations. By default, normal disk I/O operations are used but these can be overloaded @@ -8021,7 +8123,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="VFSOPTIONS"/>vfs options (S)</term> + <term><anchor id="VFSOPTIONS">vfs options (S)</term> <listitem><para>This parameter allows parameters to be passed to the vfs layer at initialization time. See also <link linkend="VFSOBJECT"><parameter> @@ -8034,7 +8136,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="VOLUME"/>volume (S)</term> + <term><anchor id="VOLUME">volume (S)</term> <listitem><para> This allows you to override the volume label returned for a share. Useful for CDROMs with installation programs that insist on a particular volume label.</para> @@ -8046,7 +8148,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WIDELINKS"/>wide links (S)</term> + <term><anchor id="WIDELINKS">wide links (S)</term> <listitem><para>This parameter controls whether or not links in the UNIX file system may be followed by the server. Links that point to areas within the directory tree exported by the @@ -8065,10 +8167,9 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINBINDCACHETIME"/>winbind cache time (G)</term> - <listitem><para>This parameter specifies the number of - seconds the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon will cache + <term><anchor id="WINBINDCACHETIME">winbind cache time (G)</term> + <listitem><para>This parameter specifies the number of seconds the + <ulink url="winbindd.8.html">winbindd(8)</ulink> daemon will cache user and group information before querying a Windows NT server again.</para> @@ -8078,10 +8179,11 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINBINDENUMUSERS"/>winbind enum users (G)</term> - <listitem><para>On large installations using <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> it may be - necessary to suppress the enumeration of users through the <command>setpwent()</command>, + <term><anchor id="WINBINDENUMUSERS">winbind enum users (G)</term> + <listitem><para>On large installations using + <ulink url="winbindd.8.html">winbindd(8)</ulink> it may be + necessary to suppress the enumeration of users through the + <command> setpwent()</command>, <command>getpwent()</command> and <command>endpwent()</command> group of system calls. If the <parameter>winbind enum users</parameter> parameter is @@ -8099,10 +8201,11 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ </varlistentry> <varlistentry> - <term><anchor id="WINBINDENUMGROUPS"/>winbind enum groups (G)</term> - <listitem><para>On large installations using <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> it may be necessary to suppress - the enumeration of groups through the <command>setgrent()</command>, + <term><anchor id="WINBINDENUMGROUPS">winbind enum groups (G)</term> + <listitem><para>On large installations using + <ulink url="winbindd.8.html">winbindd(8)</ulink> it may be + necessary to suppress the enumeration of groups through the + <command> setgrent()</command>, <command>getgrent()</command> and <command>endgrent()</command> group of system calls. If the <parameter>winbind enum groups</parameter> parameter is @@ -8119,10 +8222,10 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINBINDGID"/>winbind gid (G)</term> + <term><anchor id="WINBINDGID">winbind gid (G)</term> <listitem><para>The winbind gid parameter specifies the range of group - ids that are allocated by the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon. This range of group ids should have no + ids that are allocated by the <ulink url="winbindd.8.html"> + winbindd(8)</ulink> daemon. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.</para> @@ -8135,7 +8238,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINBINDSEPARATOR"/>winbind separator (G)</term> + <term><anchor id="WINBINDSEPARATOR">winbind separator (G)</term> <listitem><para>This parameter allows an admin to define the character used when listing a username of the form of <replaceable>DOMAIN </replaceable>\<replaceable>user</replaceable>. This parameter @@ -8156,10 +8259,10 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINBINDUID"/>winbind uid (G)</term> + <term><anchor id="WINBINDUID">winbind uid (G)</term> <listitem><para>The winbind gid parameter specifies the range of group - ids that are allocated by the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon. This range of ids should have no + ids that are allocated by the <ulink url="winbindd.8.html"> + winbindd(8)</ulink> daemon. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise.</para> @@ -8172,10 +8275,12 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINBINDUSEDEFAULTDOMAIN"/>winbind use default domain (G)</term> - <listitem><para>This parameter specifies whether the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon should operate on users - without domain component in their username. + <term>winbind use default domain</term> + + <term><anchor id="WINBINDUSEDEFAULTDOMAIN">winbind use default domain (G)</term> + <listitem><para>This parameter specifies whether the <ulink url="winbindd.8.html"> + winbindd(8)</ulink> + daemon should operate on users without domain component in their username. Users without a domain component are treated as is part of the winbindd server's own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system.</para> @@ -8188,7 +8293,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINSHOOK"/>wins hook (G)</term> + <term><anchor id="WINSHOOK">wins hook (G)</term> <listitem><para>When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database. The primary use for this option is to allow the @@ -8236,7 +8341,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINSPROXY"/>wins proxy (G)</term> + <term><anchor id="WINSPROXY">wins proxy (G)</term> <listitem><para>This is a boolean that controls if <ulink url="nmbd.8.html">nmbd(8)</ulink> will respond to broadcast name queries on behalf of other hosts. You may need to set this @@ -8250,10 +8355,10 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINSSERVER"/>wins server (G)</term> + <term><anchor id="WINSSERVER">wins server (G)</term> <listitem><para>This specifies the IP address (or DNS name: IP - address for preference) of the WINS server that <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> should register with. If you have a WINS server on + address for preference) of the WINS server that <ulink url="nmbd.8.html"> + nmbd(8)</ulink> should register with. If you have a WINS server on your network then you should set this to the WINS server's IP.</para> <para>You should point this at your WINS server if you have a @@ -8263,7 +8368,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly.</para> - <para>See the documentation file <ulink url="improved-browsing.html">BROWSING</ulink> + <para>See the documentation file <filename>BROWSING.txt</filename> in the docs/ directory of your Samba source distribution.</para> <para>Default: <emphasis>not enabled</emphasis></para> @@ -8274,9 +8379,9 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINSSUPPORT"/>wins support (G)</term> - <listitem><para>This boolean controls if the <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> process in Samba will act as a WINS server. You should + <term><anchor id="WINSSUPPORT">wins support (G)</term> + <listitem><para>This boolean controls if the <ulink url="nmbd.8.html"> + nmbd(8)</ulink> process in Samba will act as a WINS server. You should not set this to <constant>yes</constant> unless you have a multi-subnetted network and you wish a particular <command>nmbd</command> to be your WINS server. Note that you should <emphasis>NEVER</emphasis> set this to <constant>yes</constant> @@ -8289,7 +8394,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WORKGROUP"/>workgroup (G)</term> + <term><anchor id="WORKGROUP">workgroup (G)</term> <listitem><para>This controls what workgroup your server will appear to be in when queried by clients. Note that this parameter also controls the Domain name used with the <link @@ -8305,7 +8410,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WRITABLE"/>writable (S)</term> + <term><anchor id="WRITABLE">writable (S)</term> <listitem><para>Synonym for <link linkend="WRITEABLE"><parameter> writeable</parameter></link> for people who can't spell :-).</para> </listitem> @@ -8314,7 +8419,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WRITECACHESIZE"/>write cache size (S)</term> + <term><anchor id="WRITECACHESIZE">write cache size (S)</term> <listitem><para>If this integer parameter is set to non-zero value, Samba will create an in-memory cache for each oplocked file (it does <emphasis>not</emphasis> do this for @@ -8346,7 +8451,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WRITELIST"/>write list (S)</term> + <term><anchor id="WRITELIST">write list (S)</term> <listitem><para>This is a list of users that are given read-write access to a service. If the connecting user is in this list then they will be given write access, no matter what the <link @@ -8371,7 +8476,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WINSPARTNERS"/>wins partners (G)</term> + <term><anchor id="WINSPARTNERS">wins partners (G)</term> <listitem><para>A space separated list of partners' IP addresses for WINS replication. WINS partners are always defined as push/pull partners as defining only one way WINS replication is unreliable. @@ -8387,7 +8492,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WRITEOK"/>write ok (S)</term> + <term><anchor id="WRITEOK">write ok (S)</term> <listitem><para>Inverted synonym for <link linkend="READONLY"><parameter> read only</parameter></link>.</para> </listitem> @@ -8396,7 +8501,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WRITERAW"/>write raw (G)</term> + <term><anchor id="WRITERAW">write raw (G)</term> <listitem><para>This parameter controls whether or not the server will support raw write SMB's when transferring data from clients. You should never need to change this parameter.</para> @@ -8408,7 +8513,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <varlistentry> - <term><anchor id="WRITEABLE"/>writeable (S)</term> + <term><anchor id="WRITEABLE">writeable (S)</term> <listitem><para>Inverted synonym for <link linkend="READONLY"><parameter> read only</parameter></link>.</para> </listitem> @@ -8428,8 +8533,8 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ problem - but be aware of the possibility.</para> <para>On a similar note, many clients - especially DOS clients - - limit service names to eight characters. <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> has no such limitation, but attempts to connect from such + limit service names to eight characters. <ulink url="smbd.8.html">smbd(8) + </ulink> has no such limitation, but attempts to connect from such clients will fail if they truncate the service names. For this reason you should probably keep your service names down to eight characters in length.</para> @@ -8444,22 +8549,22 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <refsect1> <title>VERSION</title> - <para>This man page is correct for version 3.0 of the Samba suite.</para> + <para>This man page is correct for version 3.0 of + the Samba suite.</para> </refsect1> <refsect1> <title>SEE ALSO</title> - <para> - <citerefentry><refentrytitle>samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>swat</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmblookup</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>.</para> + <para><ulink url="samba.7.html">samba(7)</ulink>, + <ulink url="smbpasswd.8.html"><command>smbpasswd(8)</command></ulink>, + <ulink url="swat.8.html"><command>swat(8)</command></ulink>, + <ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="nmbd.8.html"><command>nmbd(8)</command></ulink>, + <ulink url="smbclient.1.html"><command>smbclient(1)</command></ulink>, + <ulink url="nmblookup.1.html"><command>nmblookup(1)</command></ulink>, + <ulink url="testparm.1.html"><command>testparm(1)</command></ulink>, + <ulink url="testprns.1.html"><command>testprns(1)</command></ulink> + </para> </refsect1> <refsect1> @@ -8472,11 +8577,11 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbcacls.1.sgml b/docs/docbook/manpages/smbcacls.1.sgml index 5e0e6c80e9..766d2a78b1 100644 --- a/docs/docbook/manpages/smbcacls.1.sgml +++ b/docs/docbook/manpages/smbcacls.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbcacls.1"> +<refentry id="smbcacls"> <refmeta> <refentrytitle>smbcacls</refentrytitle> @@ -32,8 +32,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>The <command>smbcacls</command> program manipulates NT Access Control Lists (ACLs) on SMB file shares. </para> @@ -90,8 +90,7 @@ <listitem><para>Specifies a username used to connect to the specified service. The username may be of the form "username" in which case the user is prompted to enter in a password and the - workgroup specified in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file is + workgroup specified in the <filename>smb.conf</filename> file is used, or "username%password" or "DOMAIN\username%password" and the password and workgroup names are used as provided. </para></listitem> </varlistentry> @@ -148,12 +147,12 @@ <para>The format of an ACL is one or more ACL entries separated by either commas or newlines. An ACL entry is one of the following: </para> -<para><programlisting> + <para><programlisting> REVISION:<revision number> OWNER:<sid or name> GROUP:<sid or name> ACL:<sid or name>:<type>/<flags>/<mask> -</programlisting></para> + </programlisting></para> <para>The revision of the ACL specifies the internal Windows @@ -166,22 +165,24 @@ ACL:<sid or name>:<type>/<flags>/<mask> otherwise the name specified is resolved using the server on which the file or directory resides. </para> - <para>ACLs specify permissions granted to the SID. This SID again - can be specified in CWS-1-x-y-z format or as a name in which case - it is resolved against the server on which the file or directory - resides. The type, flags and mask values determine the type of - access granted to the SID. </para> - - <para>The type can be either 0 or 1 corresponding to ALLOWED or - DENIED access to the SID. The flags values are generally - zero for file ACLs and either 9 or 2 for directory ACLs. Some - common flags are: </para> - - <itemizedlist> - <listitem><para><constant>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</constant></para></listitem> - <listitem><para><constant>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</constant></para></listitem> - <listitem><para><constant>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</constant></para></listitem> - <listitem><para><constant>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</constant></para></listitem> + <para>ACLs specify permissions granted to the SID. This SID again + can be specified in CWS-1-x-y-z format or as a name in which case + it is resolved against the server on which the file or directory + resides. The type, flags and mask values determine the type of + access granted to the SID. </para> + + <para>The type can be either 0 or 1 corresponding to ALLOWED or + DENIED access to the SID. The flags values are generally + zero for file ACLs and either 9 or 2 for directory ACLs. Some + common flags are: </para> + + <itemizedlist> + <listitem><para>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</para></listitem> + <listitem><para>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</para></listitem> + <listitem><para>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 + </para></listitem> + <listitem><para>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</para> + </listitem> </itemizedlist> <para>At present flags can only be specified as decimal or @@ -232,7 +233,8 @@ ACL:<sid or name>:<type>/<flags>/<mask> <refsect1> <title>VERSION</title> - <para>This man page is correct for version 2.2 of the Samba suite.</para> + <para>This man page is correct for version 2.2 of + the Samba suite.</para> </refsect1> <refsect1> @@ -247,8 +249,7 @@ ACL:<sid or name>:<type>/<flags>/<mask> and Tim Potter.</para> <para>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.</para> + by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbclient.1.sgml b/docs/docbook/manpages/smbclient.1.sgml index a08f6999e4..43994a4529 100644 --- a/docs/docbook/manpages/smbclient.1.sgml +++ b/docs/docbook/manpages/smbclient.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbclient.1"> +<refentry id="smbclient"> <refmeta> <refentrytitle>smbclient</refentrytitle> @@ -38,20 +38,18 @@ <arg choice="opt">-R <name resolve order></arg> <arg choice="opt">-s <smb config file></arg> <arg choice="opt">-T<c|x>IXFqgbNan</arg> - <arg choice="opt">-k</arg> </cmdsynopsis> </refsynopsisdiv> <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>smbclient</command> is a client that can 'talk' to an SMB/CIFS server. It offers an interface - similar to that of the ftp program (see <citerefentry><refentrytitle>ftp</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>). + similar to that of the ftp program (see <command>ftp(1)</command>). Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server @@ -83,9 +81,7 @@ <para>The server name is looked up according to either the <parameter>-R</parameter> parameter to <command>smbclient</command> or - using the name resolve order parameter in - the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file, + using the name resolve order parameter in the <filename>smb.conf</filename> file, allowing an administrator to change the order and methods by which server names are looked up. </para></listitem> </varlistentry> @@ -117,17 +113,15 @@ <varlistentry> <term>-s smb.conf</term> - <listitem><para>Specifies the location of the all - important <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. </para></listitem> + <listitem><para>Specifies the location of the all important + <filename>smb.conf</filename> file. </para></listitem> </varlistentry> <varlistentry> <term>-O socket options</term> <listitem><para>TCP socket options to set on the client - socket. See the socket options parameter in - the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> manual page for the list of valid + socket. See the socket options parameter in the <filename> + smb.conf (5)</filename> manpage for the list of valid options. </para></listitem> </varlistentry> @@ -140,51 +134,44 @@ string of different name resolution options.</para> <para>The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows:</para> + cause names to be resolved as follows :</para> <itemizedlist> - <listitem><para><constant>lmhosts</constant>: Lookup an IP + <listitem><para><constant>lmhosts</constant> : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has - no name type attached to the NetBIOS name (see - the <citerefentry><refentrytitle>lmhosts</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for details) then - any name type matches for lookup.</para> - </listitem> - - <listitem><para><constant>host</constant>: Do a standard host + no name type attached to the NetBIOS name (see the <ulink + url="lmhosts.5.html">lmhosts(5)</ulink> for details) then + any name type matches for lookup.</para></listitem> + + <listitem><para><constant>host</constant> : Do a standard host name to IP address resolution, using the system <filename>/etc/hosts </filename>, NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the <filename>/etc/nsswitch.conf</filename> file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise - it is ignored.</para> - </listitem> - - <listitem><para><constant>wins</constant>: Query a name with + it is ignored.</para></listitem> + + <listitem><para><constant>wins</constant> : Query a name with the IP address listed in the <parameter>wins server</parameter> parameter. If no WINS server has - been specified this method will be ignored.</para> - </listitem> - - <listitem><para><constant>bcast</constant>: Do a broadcast on + been specified this method will be ignored.</para></listitem> + + <listitem><para><constant>bcast</constant> : Do a broadcast on each of the known local interfaces listed in the <parameter>interfaces</parameter> parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally - connected subnet.</para> - </listitem> + connected subnet.</para></listitem> </itemizedlist> <para>If this parameter is not set then the name resolve order - defined in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file parameter + defined in the <filename>smb.conf</filename> file parameter (name resolve order) will be used. </para> <para>The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the <parameter>name resolve order - </parameter> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file the name resolution + </parameter> parameter of the <filename>smb.conf</filename> file the name resolution methods will be attempted in this order. </para></listitem> </varlistentry> @@ -215,8 +202,8 @@ <parameter>-I</parameter> options useful, as they allow you to control the FROM and TO parts of the message. </para> - <para>See the <parameter>message command</parameter> parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for a description of how to handle incoming + <para>See the message command parameter in the <filename> + smb.conf(5)</filename> for a description of how to handle incoming WinPopup messages in Samba. </para> <para><emphasis>Note</emphasis>: Copy WinPopup into the startup group @@ -392,11 +379,11 @@ password used in the connection. The format of the file is </para> -<para><programlisting> + <para><programlisting> username = <value> password = <value> domain = <value> -</programlisting></para> + </programlisting></para> <para>If the domain parameter is missing the current workgroup name @@ -448,9 +435,9 @@ domain = <value> <varlistentry> <term>-W WORKGROUP</term> <listitem><para>Override the default workgroup (domain) specified - in the workgroup parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file for this connection. This may be - needed to connect to some servers. </para></listitem> + in the workgroup parameter of the <filename>smb.conf</filename> + file for this connection. This may be needed to connect to some + servers. </para></listitem> </varlistentry> @@ -532,7 +519,7 @@ domain = <value> <para><emphasis>Tar Filenames</emphasis></para> - <para>All file names can be given as DOS path names (with '\\' + <para>All file names can be given as DOS path names (with '\' as the component separator) or as UNIX path names (with '/' as the component separator). </para> @@ -588,14 +575,6 @@ domain = <value> <para>This is particularly useful in scripts and for printing stdin to the server, e.g. <command>-c 'print -'</command>. </para></listitem> </varlistentry> - - <varlistentry> - <term>-k</term> - <listitem><para> - Try to authenticate with kerberos. Only useful in - an Active Directory environment. - </para></listitem> - </varlistentry> </variablelist> </refsect1> @@ -608,7 +587,7 @@ domain = <value> <para><prompt>smb:\> </prompt></para> - <para>The backslash ("\\") indicates the current working directory + <para>The backslash ("\") indicates the current working directory on the server, and will change if the current working directory is changed. </para> @@ -1061,8 +1040,8 @@ domain = <value> and writeable only by the user. </para> <para>To test the client, you will need to know the name of a - running SMB/CIFS server. It is possible to run <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> as an ordinary user - running that server as a daemon + running SMB/CIFS server. It is possible to run <command>smbd(8) + </command> as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server. </para> </refsect1> @@ -1084,7 +1063,8 @@ domain = <value> <refsect1> <title>VERSION</title> - <para>This man page is correct for version 2.2 of the Samba suite.</para> + <para>This man page is correct for version 2.2 of + the Samba suite.</para> </refsect1> @@ -1098,11 +1078,11 @@ domain = <value> <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbcontrol.1.sgml b/docs/docbook/manpages/smbcontrol.1.sgml index 6632e07269..166ef63e87 100644 --- a/docs/docbook/manpages/smbcontrol.1.sgml +++ b/docs/docbook/manpages/smbcontrol.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbcontrol.1"> +<refentry id="smbcontrol"> <refmeta> <refentrytitle>smbcontrol</refentrytitle> @@ -29,14 +29,14 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>smbcontrol</command> is a very small program, which - sends messages to a <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, a <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, or a <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon running on the system.</para> + sends messages to an <ulink url="smbd.8.html">smbd(8)</ulink>, + an <ulink url="nmbd.8.html">nmbd(8)</ulink> + or a <ulink url="winbindd.8.html">winbindd(8)</ulink> + daemon running on the system.</para> </refsect1> @@ -54,7 +54,8 @@ <varlistentry> <term>destination</term> - <listitem><para>One of <parameter>nmbd</parameter>, <parameter>smbd</parameter> or a process ID.</para> + <listitem><para>One of <parameter>nmbd</parameter> + <parameter>smbd</parameter> or a process ID.</para> <para>The <parameter>smbd</parameter> destination causes the message to "broadcast" to all smbd daemons.</para> @@ -189,9 +190,9 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>.</para> + <para><ulink url="nmbd.8.html"><command>nmbd(8)</command></ulink>, + and <ulink url="smbd.8.html"><command>smbd(8)</command></ulink>. + </para> </refsect1> <refsect1> @@ -204,11 +205,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbd.8.sgml b/docs/docbook/manpages/smbd.8.sgml index 32837ba903..9fb80901be 100644 --- a/docs/docbook/manpages/smbd.8.sgml +++ b/docs/docbook/manpages/smbd.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbd.8"> +<refentry id="smbd"> <refmeta> <refentrytitle>smbd</refentrytitle> @@ -32,8 +32,7 @@ <refsect1> <title>DESCRIPTION</title> - <para>This program is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This program is part of the Samba suite.</para> <para><command>smbd</command> is the server daemon that provides filesharing and printing services to Windows clients. @@ -47,14 +46,15 @@ <para>An 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 <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>. This man page will not describe the + services (see <ulink url="smb.conf.5.html"><filename>smb.conf(5) + </filename></ulink>. This man page will not describe the services, but will concentrate on the administrative aspects of running the server.</para> <para>Please note that there are significant security - implications to running this server, and the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> manual page should be regarded as mandatory reading before + implications to running this server, and the <ulink + url="smb.conf.5.html"><filename>smb.conf(5)</filename></ulink> + manpage should be regarded as mandatory reading before proceeding with installation.</para> <para>A session is created whenever a client requests one. @@ -160,9 +160,9 @@ data, most of which is extremely cryptic.</para> <para>Note that specifying this parameter here will - override the <ulink url="smb.conf.5.html#loglevel"><parameter>log - level</parameter></ulink> parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file.</para> + override the <ulink url="smb.conf.5.html#loglevel">log + level</ulink> parameter in the <ulink url="smb.conf.5.html"> + <filename>smb.conf(5)</filename></ulink> file.</para> </listitem> </varlistentry> @@ -175,9 +175,9 @@ messages from the running server. The log file generated is never removed by the server although its size may be controlled by the <ulink - url="smb.conf.5.html#maxlogsize"><parameter>max log size</parameter></ulink> - option in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. <emphasis>Beware:</emphasis> + url="smb.conf.5.html#maxlogsize">max log size</ulink> + option in the <ulink url="smb.conf.5.html"><filename> + smb.conf(5)</filename></ulink> file. <emphasis>Beware:</emphasis> If the directory specified does not exist, <command>smbd</command> will log to the default debug log location defined at compile time. </para> @@ -189,9 +189,9 @@ <varlistentry> <term>-O <socket options></term> <listitem><para>See the <ulink - url="smb.conf.5.html#socketoptions"><parameter>socket options</parameter></ulink> - parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file for details.</para></listitem> + url="smb.conf.5.html#socketoptions">socket options</ulink> + parameter in the <ulink url="smb.conf.5.html"><filename>smb.conf(5) + </filename></ulink> file for details.</para></listitem> </varlistentry> <varlistentry> @@ -226,8 +226,8 @@ 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 <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for more information. + to provide. See <ulink url="smb.conf.5.html"><filename> + smb.conf(5)</filename></ulink> for more information. The default configuration file name is determined at compile time.</para></listitem> </varlistentry> @@ -243,7 +243,7 @@ <listitem><para>If the server is to be run by the <command>inetd</command> meta-daemon, this file must contain suitable startup information for the - meta-daemon. See the <ulink url="install.html">"How to Install and Test SAMBA"</ulink> + meta-daemon. See the <ulink url="UNIX_INSTALL.html">UNIX_INSTALL.html</ulink> document for details. </para></listitem> </varlistentry> @@ -255,7 +255,7 @@ <para>If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server. See the <ulink url="install.html">"How to Install and Test SAMBA"</ulink> + sequence for the server. See the <ulink url="UNIX_INSTALL.html">UNIX_INSTALL.html</ulink> document for details.</para></listitem> </varlistentry> @@ -265,20 +265,21 @@ meta-daemon <command>inetd</command>, 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). - See the <ulink url="install.html">"How to Install and Test SAMBA"</ulink> + See the <ulink url="UNIX_INSTALL.html">UNIX_INSTALL.html</ulink> document for details.</para></listitem> </varlistentry> <varlistentry> <term><filename>/usr/local/samba/lib/smb.conf</filename></term> - <listitem><para>This is the default location of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> server configuration file. Other common places that systems + <listitem><para>This is the default location of the + <ulink url="smb.conf.5.html"><filename>smb.conf</filename></ulink> + server configuration file. Other common places that systems install this file are <filename>/usr/samba/lib/smb.conf</filename> - and <filename>/etc/samba/smb.conf</filename>.</para> + and <filename>/etc/smb.conf</filename>.</para> <para>This file describes all the services the server - is to make available to clients. See <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for more information.</para> + is to make available to clients. See <ulink url="smb.conf.5.html"> + <filename>smb.conf(5)</filename></ulink> for more information.</para> </listitem> </varlistentry> </variablelist> @@ -316,9 +317,9 @@ <para>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 <ulink url="smb.conf.5.html#OBEYPAMRESRICTIONS"><parameter>obey - pam restricions</parameter></ulink> <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> paramater. When this is set, the following restrictions apply: + by the limitations of the SMB protocol and the + <ulink url="smb.conf.5.html#OBEYPAMRESRICTIONS">obey pam restricions</ulink> + smb.conf paramater. When this is set, the following restrictions apply: </para> <itemizedlist> @@ -378,9 +379,9 @@ it to die on its own.</para> <para>The debug log level of <command>smbd</command> may be raised - or lowered using <citerefentry><refentrytitle>smbcontrol</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> program (SIGUSR[1|2] signals are no longer - used since Samba 2.2). This is to allow transient problems to be diagnosed, + or lowered using <ulink url="smbcontrol.1.html"><command>smbcontrol(1) + </command></ulink> program (SIGUSR[1|2] signals are no longer used in + Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level.</para> <para>Note that as the signal handlers send a debug write, @@ -393,15 +394,14 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>hosts_access</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>inetd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, and the - Internet RFC's <filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>. + <para>hosts_access(5), <command>inetd(8)</command>, + <ulink url="nmbd.8.html"><command>nmbd(8)</command></ulink>, + <ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename> + </ulink>, <ulink url="smbclient.1.html"><command>smbclient(1) + </command></ulink>, <ulink url="testparm.1.html"><command> + testparm(1)</command></ulink>, <ulink url="testprns.1.html"> + <command>testprns(1)</command></ulink>, and the Internet RFC's + <filename>rfc1001.txt</filename>, <filename>rfc1002.txt</filename>. In addition the CIFS (formerly SMB) specification is available as a link from the Web page <ulink url="http://samba.org/cifs/"> http://samba.org/cifs/</ulink>.</para> @@ -417,11 +417,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbgroupedit.8.sgml b/docs/docbook/manpages/smbgroupedit.8.sgml index 6c489bb785..188218c249 100644 --- a/docs/docbook/manpages/smbgroupedit.8.sgml +++ b/docs/docbook/manpages/smbgroupedit.8.sgml @@ -1,11 +1,15 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbgroupedit.8"> +<refentry id="smbgroupedit"> <refmeta> <refentrytitle>smbgroupedit</refentrytitle> <manvolnum>8</manvolnum> </refmeta> + +<!-- **************************************************** +** Name and Options ** +**************************************************** --> <refnamediv> <refname>smbgroupedit</refname> <refpurpose>Query/set/change UNIX - Windows NT group mapping</refpurpose> @@ -21,13 +25,17 @@ +<!-- **************************************************** +** Description ** +**************************************************** --> <refsect1> <title>DESCRIPTION</title> <para> -This program is part of the <citerefentry><refentrytitle>Samba</refentrytitle> -<manvolnum>7</manvolnum></citerefentry> suite.</para> +This program is part of the <ulink url="samba.7.html">Samba</ulink> +suite. +</para> <para> The smbgroupedit command allows for mapping unix groups @@ -62,8 +70,8 @@ etc. Privilege : </programlisting></para> -<para>For example: -<programlisting> +<para>For examples,</para> +<para><programlisting> Users SID : S-1-5-32-545 Unix group: -1 @@ -83,8 +91,9 @@ Users NTGroupName(SID) -> UnixGroupName </programlisting></para> -<para>For example: -<programlisting> +<para>For example,</para> + +<para><programlisting> Users (S-1-5-32-545) -> -1 </programlisting></para> @@ -100,6 +109,8 @@ Users (S-1-5-32-545) -> -1 +<!-- **************************************************** +**************************************************** --> <refsect1> <title>FILES</title> @@ -109,6 +120,8 @@ Users (S-1-5-32-545) -> -1 +<!-- **************************************************** +**************************************************** --> <refsect1> <title>EXIT STATUS</title> @@ -150,45 +163,65 @@ the 'Domain Admins' Global group: <para>domadm:x:502:joe,john,mary</para> </listitem> - <listitem><para>map this domadm group to the 'domain admins' group:</para> + <listitem><para>map this domadm group to the 'domain admins' group: + </para> <orderedlist> - <listitem><para>Get the SID for the Windows NT "Domain Admins" group:</para> + <listitem><para>Get the SID for the Windows NT "Domain Admins" + group:</para> + <para><programlisting> <prompt>root# </prompt><command>smbgroupedit -vs | grep "Domain Admins"</command> Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> -1 -</programlisting></para></listitem> +</programlisting></para> +</listitem> <listitem><para>map the unix domadm group to the Windows NT "Domain Admins" group, by running the command: -<programlisting> + </para> + +<para><programlisting> <prompt>root# </prompt><command>smbgroupedit \ -c S-1-5-21-1108995562-3116817432-1375597819-512 \ -u domadm -td</command> </programlisting></para> - <para><emphasis>warning:</emphasis> don't copy and paste this sample, the + <para> + <emphasis>warning:</emphasis> don't copy and paste this sample, the Domain Admins SID (the S-1-5-21-...-512) is different for every PDC. - </para> </listitem> + </para> + </listitem> </orderedlist> </listitem> </orderedlist> <para> To verify that your mapping has taken effect: -<programlisting> +</para> + +<para><programlisting> <prompt>root# </prompt><command>smbgroupedit -vs|grep "Domain Admins"</command> Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> domadm </programlisting></para> -<para>To give access to a certain directory on a domain member machine (an +<para> +To give access to a certain directory on a domain member machine (an NT/W2K or a samba server running winbind) to some users who are member of a group on your samba PDC, flag that group as a domain group: -<programlisting> +</para> + +<para><programlisting> <prompt>root# </prompt><command>smbgroupedit -a unixgroup -td</command> </programlisting></para> + + </refsect1> + + + +<!-- **************************************************** +**************************************************** --> <refsect1> <title>VERSION</title> @@ -199,16 +232,22 @@ the Samba suite. </para> </refsect1> +<!-- **************************************************** +**************************************************** --> + <refsect1> <title>SEE ALSO</title> <para> -<citerefentry><refentrytitle>smb.conf</refentrytitle> -<manvolnum>5</manvolnum></citerefentry></para> +<ulink url="smb.conf.5.html">smb.conf(5)</ulink> +</para> </refsect1> +<!-- **************************************************** +**************************************************** --> + <refsect1> <title>AUTHOR</title> @@ -222,8 +261,7 @@ to the way the Linux kernel is developed. <para> <command>smbgroupedit</command> was written by Jean Francois Micouleau. The current set of manpages and documentation is maintained -by the Samba Team in the same fashion as the Samba source code. The conversion -to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para> +by the Samba Team in the same fashion as the Samba source code.</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbmnt.8.sgml b/docs/docbook/manpages/smbmnt.8.sgml index 6d48b12b9b..55b66d5d25 100644 --- a/docs/docbook/manpages/smbmnt.8.sgml +++ b/docs/docbook/manpages/smbmnt.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbmnt.8"> +<refentry id="smbmnt"> <refmeta> <refentrytitle>smbmnt</refentrytitle> @@ -38,8 +38,8 @@ by the user, and that the user has write permission on.</para> <para>The <command>smbmnt</command> program is normally invoked - by <citerefentry><refentrytitle>smbmount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>. It should not be invoked directly by users. </para> + by <ulink url="smbmount.8.html"><command>smbmount(8)</command> + </ulink>. It should not be invoked directly by users. </para> <para>smbmount searches the normal PATH for smbmnt. You must ensure that the smbmnt version in your path matches the smbmount used.</para> @@ -107,8 +107,7 @@ </para> <para>The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</para> + by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbmount.8.sgml b/docs/docbook/manpages/smbmount.8.sgml index d17e4e6bcf..c4b91a5572 100644 --- a/docs/docbook/manpages/smbmount.8.sgml +++ b/docs/docbook/manpages/smbmount.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbmount.8"> +<refentry id="smbmount"> <refmeta> <refentrytitle>smbmount</refentrytitle> @@ -26,8 +26,7 @@ <para><command>smbmount</command> mounts a Linux SMB filesystem. It is usually invoked as <command>mount.smbfs</command> by - the <citerefentry><refentrytitle>mount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> command when using the + the <command>mount(8)</command> command when using the "-t smbfs" option. This command only works in Linux, and the kernel must support the smbfs filesystem. </para> @@ -40,12 +39,11 @@ <para><command>smbmount</command> is a daemon. After mounting it keeps running until the mounted smbfs is umounted. It will log things that happen when in daemon mode using the "machine name" smbmount, so - typically this output will end up in <filename>log.smbmount</filename>. The <command> - smbmount</command> process may also be called mount.smbfs.</para> + typically this output will end up in <filename>log.smbmount</filename>. The + <command>smbmount</command> process may also be called mount.smbfs.</para> <para><emphasis>NOTE:</emphasis> <command>smbmount</command> - calls <citerefentry><refentrytitle>smbmnt</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to do the actual mount. You + calls <command>smbmnt(8)</command> to do the actual mount. You must make sure that <command>smbmnt</command> is in the path so that it can be found. </para> @@ -86,12 +84,15 @@ <varlistentry> <term>credentials=<filename></term> - <listitem><para>specifies a file that contains a username and/or password. -The format of the file is: -<programlisting> -username = <value> -password = <value> -</programlisting></para> + <listitem><para>specifies a file that contains a username + and/or password. The format of the file is:</para> + + <para> + <programlisting> + username = <value> + password = <value> + </programlisting> + </para> <para>This is preferred over having passwords in plaintext in a shared file, such as <filename>/etc/fstab</filename>. Be sure to protect any @@ -173,8 +174,8 @@ password = <value> <varlistentry> <term>sockopt=<arg></term> <listitem><para>sets the TCP socket options. See the <ulink - url="smb.conf.5.html#SOCKETOPTIONS"><citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></ulink> <parameter>socket options</parameter> option. + url="smb.conf.5.html#SOCKETOPTIONS"><filename>smb.conf + </filename></ulink> <parameter>socket options</parameter> option. </para></listitem> </varlistentry> @@ -297,9 +298,10 @@ password = <value> <para>FreeBSD also has a smbfs, but it is not related to smbmount</para> - <para>For Solaris, HP-UX and others you may want to look at <citerefentry><refentrytitle>smbsh</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> or at other solutions, such as - Sharity or perhaps replacing the SMB server with a NFS server.</para> + <para>For Solaris, HP-UX and others you may want to look at + <ulink url="smbsh.1.html"><command>smbsh(1)</command></ulink> or at other + solutions, such as sharity or perhaps replacing the SMB server with + a NFS server.</para> </refsect1> @@ -319,8 +321,7 @@ password = <value> </para> <para>The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</para> + by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbpasswd.5.sgml b/docs/docbook/manpages/smbpasswd.5.sgml index f78e986bef..5c80ac4c06 100644 --- a/docs/docbook/manpages/smbpasswd.5.sgml +++ b/docs/docbook/manpages/smbpasswd.5.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbpasswd.5"> +<refentry id="smbpasswd"> <refmeta> <refentrytitle>smbpasswd</refentrytitle> @@ -19,8 +19,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the @@ -122,7 +122,7 @@ the attributes of the users account. In the Samba 2.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). - The contents of this field may be any of the following characters: + The contents of this field may be any of the characters. </para> <itemizedlist> @@ -136,11 +136,12 @@ Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the <parameter> null passwords</parameter> parameter is set in the <ulink - url="smb.conf.5.html#NULLPASSWORDS"><citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></ulink> config file. </para></listitem> + url="smb.conf.5.html#NULLPASSWORDS"><filename>smb.conf(5) + </filename></ulink> config file. </para></listitem> <listitem><para><emphasis>D</emphasis> - This means the account - is disabled and no SMB/CIFS logins will be allowed for this user. </para></listitem> + is disabled and no SMB/CIFS logins will be allowed for + this user. </para></listitem> <listitem><para><emphasis>W</emphasis> - This means this account is a "Workstation Trust" account. This kind of account is used @@ -177,9 +178,8 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>, and + <para><ulink url="smbpasswd.8.html"><command>smbpasswd(8)</command></ulink>, + <ulink url="samba.7.html">samba(7)</ulink>, and the Internet RFC1321 for details on the MD4 algorithm. </para> </refsect1> @@ -194,11 +194,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbpasswd.8.sgml b/docs/docbook/manpages/smbpasswd.8.sgml index 5d475cf08c..8e6d925ae0 100644 --- a/docs/docbook/manpages/smbpasswd.8.sgml +++ b/docs/docbook/manpages/smbpasswd.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbpasswd.8"> +<refentry id="smbpasswd"> <refmeta> <refentrytitle>smbpasswd</refentrytitle> @@ -37,27 +37,25 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>The smbpasswd program has several different - functions, depending on whether it is run by the <emphasis>root</emphasis> user - or not. When run as a normal user it allows the user to change + functions, depending on whether it is run by the <emphasis>root</emphasis> + user or not. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords. </para> <para>By default (when run with no arguments) it will attempt to change the current user's SMB password on the local machine. This is - similar to the way the <command>passwd(1)</command> program works. <command> - smbpasswd</command> differs from how the passwd program works + similar to the way the <command>passwd(1)</command> program works. + <command>smbpasswd</command> differs from how the passwd program works however in that it is not <emphasis>setuid root</emphasis> but works in - a client-server mode and communicates with a - locally running <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>. As a consequence in order for this to + a client-server mode and communicates with a locally running + <command>smbd(8)</command>. As a consequence in order for this to succeed the smbd daemon must be running on the local machine. On a UNIX machine the encrypted SMB passwords are usually stored in - the <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. </para> + the <filename>smbpasswd(5)</filename> file. </para> <para>When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them @@ -69,13 +67,12 @@ <para>smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain - Controllers. See the (<parameter>-r</parameter>) and <parameter>-U</parameter> options - below. </para> + Controllers. See the (-r) and -U options below. </para> <para>When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to - the attributes of the user in this file to be made. When run by root, <command> - smbpasswd</command> accesses the local smbpasswd file + the attributes of the user in this file to be made. When run by root, + <command>smbpasswd</command> accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running. </para> </refsect1> @@ -124,8 +121,8 @@ <para>If the smbpasswd file is in the 'old' format (pre-Samba 2.0 format) there is no space in the user's password entry to write - this information and the command will FAIL. See <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for details on the 'old' and new password file formats. + this information and the command will FAIL. See <command>smbpasswd(5) + </command> for details on the 'old' and new password file formats. </para> <para>This option is only available when running smbpasswd as @@ -143,8 +140,7 @@ <para>If the smbpasswd file is in the 'old' format, then <command> smbpasswd</command> will FAIL to enable the account. - See <citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for + See <command>smbpasswd (5)</command> for details on the 'old' and new password file formats. </para> <para>This option is only available when running smbpasswd as root. @@ -230,15 +226,15 @@ name of the host being connected to. </para> <para>The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows: </para> + cause names to be resolved as follows : </para> <itemizedlist> - <listitem><para><constant>lmhosts</constant>: Lookup an IP + <listitem><para><constant>lmhosts</constant> : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has - no name type attached to the NetBIOS name (see the <citerefentry><refentrytitle>lmhosts</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for details) then + no name type attached to the NetBIOS name (see the <ulink + url="lmhosts.5.html">lmhosts(5)</ulink> for details) then any name type matches for lookup.</para></listitem> - <listitem><para><constant>host</constant>: Do a standard host + <listitem><para><constant>host</constant> : Do a standard host name to IP address resolution, using the system <filename>/etc/hosts </filename>, NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this @@ -247,12 +243,12 @@ type being queried is the 0x20 (server) name type, otherwise it is ignored.</para></listitem> - <listitem><para><constant>wins</constant>: Query a name with + <listitem><para><constant>wins</constant> : Query a name with the IP address listed in the <parameter>wins server</parameter> parameter. If no WINS server has been specified this method will be ignored.</para></listitem> - <listitem><para><constant>bcast</constant>: Do a broadcast on + <listitem><para><constant>bcast</constant> : Do a broadcast on each of the known local interfaces listed in the <parameter>interfaces</parameter> parameter. This is the least reliable of the name resolution methods as it depends on the @@ -260,8 +256,8 @@ </itemizedlist> <para>The default order is <command>lmhosts, host, wins, bcast</command> - and without this parameter or any entry in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file the name resolution methods will + and without this parameter or any entry in the + <filename>smb.conf</filename> file the name resolution methods will be attempted in this order. </para></listitem> </varlistentry> @@ -296,6 +292,7 @@ </varlistentry> + <varlistentry> <term>-s</term> <listitem><para>This option causes smbpasswd to be silent (i.e. @@ -315,7 +312,7 @@ switch is used to specify the password to be used with the <ulink url="smb.conf.5.html#LDAPADMINDN"><parameter>ldap admin dn</parameter></ulink>. Note that the password is stored in - the <filename>secrets.tdb</filename> and is keyed off + the <filename>private/secrets.tdb</filename> and is keyed off of the admin's DN. This means that if the value of <parameter>ldap admin dn</parameter> ever changes, the password will need to be manually updated as well. @@ -358,15 +355,14 @@ mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work. A common problem is to add a restriction to the hosts that may access the <command> - smbd</command> running on the local machine by specifying either <parameter>allow - hosts</parameter> or <parameter>deny hosts</parameter> entry in - the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file and neglecting to + smbd</command> running on the local machine by specifying a + <parameter>allow hosts</parameter> or <parameter>deny hosts</parameter> + entry in the <filename>smb.conf</filename> file and neglecting to allow "localhost" access to the smbd. </para> <para>In addition, the smbpasswd command is only useful if Samba - has been set up to use encrypted passwords. See the document <ulink url="pwencrypt.html"> - "LanMan and NT Password Encryption in Samba"</ulink> in the docs directory for details + has been set up to use encrypted passwords. See the file + <filename>ENCRYPTION.txt</filename> in the docs directory for details on how to do this. </para> </refsect1> @@ -374,14 +370,15 @@ <refsect1> <title>VERSION</title> - <para>This man page is correct for version 3.0 of the Samba suite.</para> + <para>This man page is correct for version 3.0 of + the Samba suite.</para> </refsect1> <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>.</para> + <para><ulink url="smbpasswd.5.html"><filename>smbpasswd(5)</filename></ulink>, + <ulink url="samba.7.html">samba(7)</ulink> + </para> </refsect1> <refsect1> @@ -394,11 +391,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbsh.1.sgml b/docs/docbook/manpages/smbsh.1.sgml index af080c298c..c40609be4f 100644 --- a/docs/docbook/manpages/smbsh.1.sgml +++ b/docs/docbook/manpages/smbsh.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbsh.1"> +<refentry id="smbsh"> <refmeta> <refentrytitle>smbsh</refentrytitle> @@ -29,8 +29,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>smbsh</command> allows you to access an NT filesystem using UNIX commands such as <command>ls</command>, <command> @@ -46,8 +46,7 @@ <varlistentry> <term>-W WORKGROUP</term> <listitem><para>Override the default workgroup specified in the - workgroup parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file + workgroup parameter of the <filename>smb.conf</filename> file for this session. This may be needed to connect to some servers. </para></listitem> </varlistentry> @@ -62,8 +61,7 @@ </varlistentry> <varlistentry> - <term>-P prefix</term> - <listitem><para>This option allows + <term>-P prefix</term><listitem><para>This option allows the user to set the directory prefix for SMB access. The default value if this option is not specified is <emphasis>smb</emphasis>. @@ -77,20 +75,19 @@ host names to IP addresses. The option takes a space-separated string of different name resolution options.</para> - <para>The options are: "lmhosts", "host", "wins" and "bcast". + <para>The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows :</para> <itemizedlist> - <listitem><para><constant>lmhosts</constant>: + <listitem><para><constant>lmhosts</constant> : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name - (see the <citerefentry><refentrytitle>lmhosts</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for details) - then any name type matches for lookup. + (see the <ulink url="lmhosts.5.html">lmhosts(5)</ulink> + for details) then any name type matches for lookup. </para></listitem> - <listitem><para><constant>host</constant>: + <listitem><para><constant>host</constant> : Do a standard host name to IP address resolution, using the system <filename>/etc/hosts</filename>, NIS, or DNS lookups. This method of name resolution is operating @@ -101,14 +98,14 @@ (server) name type, otherwise it is ignored. </para></listitem> - <listitem><para><constant>wins</constant>: + <listitem><para><constant>wins</constant> : Query a name with the IP address listed in the <parameter>wins server</parameter> parameter. If no WINS server has been specified this method will be ignored. </para></listitem> - <listitem><para><constant>bcast</constant>: + <listitem><para><constant>bcast</constant> : Do a broadcast on each of the known local interfaces listed in the <parameter>interfaces</parameter> parameter. This is the least reliable of the name @@ -118,15 +115,14 @@ </itemizedlist> <para>If this parameter is not set then the name resolve order - defined in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file parameter - (<parameter>name resolve order</parameter>) will be used. </para> + defined in the <filename>smb.conf</filename> file parameter + (name resolve order) will be used. </para> <para>The default order is lmhosts, host, wins, bcast. Without this parameter or any entry in the <parameter>name resolve order - </parameter> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file, the name resolution methods - will be attempted in this order. </para></listitem> + </parameter> parameter of the <filename>smb.conf</filename> + file, the name resolution methods will be attempted in this + order. </para></listitem> </varlistentry> <varlistentry> @@ -137,8 +133,7 @@ is zero.</para> <para>The higher this value, the more detail will be logged - about the activities of <citerefentry><refentrytitle>nmblookup</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>. At level + about the activities of <command>nmblookup</command>. At level 0, only critical errors and serious warnings will be logged. </para></listitem> </varlistentry> @@ -169,12 +164,13 @@ <para>To use the <command>smbsh</command> command, execute <command> smbsh</command> from the prompt and enter the username and password that authenticates you to the machine running the Windows NT - operating system. -<programlisting> -<prompt>system% </prompt><userinput>smbsh</userinput> -<prompt>Username: </prompt><userinput>user</userinput> -<prompt>Password: </prompt><userinput>XXXXXXX</userinput> -</programlisting></para> + operating system.</para> + + <para><programlisting> + <prompt>system% </prompt><userinput>smbsh</userinput> + <prompt>Username: </prompt><userinput>user</userinput> + <prompt>Password: </prompt><userinput>XXXXXXX</userinput> + </programlisting></para> <para>Any dynamically linked command you execute from @@ -192,7 +188,8 @@ <refsect1> <title>VERSION</title> - <para>This man page is correct for version 3.0 of the Samba suite.</para> + <para>This man page is correct for version 3.0 of + the Samba suite.</para> </refsect1> <refsect1> @@ -213,9 +210,9 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></para> + <para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="smb.conf.5.html">smb.conf(5)</ulink> + </para> </refsect1> <refsect1> @@ -228,11 +225,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbspool.8.sgml b/docs/docbook/manpages/smbspool.8.sgml index f30539601e..d164cb0864 100644 --- a/docs/docbook/manpages/smbspool.8.sgml +++ b/docs/docbook/manpages/smbspool.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbspool.8"> +<refentry id="smbspool"> <refmeta> <refentrytitle>smbspool</refentrytitle> @@ -27,8 +27,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>smbspool is a very small print spooling program that sends a print file to an SMB printer. The command-line arguments @@ -45,8 +45,10 @@ <itemizedlist> <listitem><para>smb://server/printer</para></listitem> <listitem><para>smb://workgroup/server/printer</para></listitem> - <listitem><para>smb://username:password@server/printer</para></listitem> - <listitem><para>smb://username:password@workgroup/server/printer</para></listitem> + <listitem><para>smb://username:password@server/printer</para> + </listitem> + <listitem><para>smb://username:password@workgroup/server/printer + </para></listitem> </itemizedlist> <para>smbspool tries to get the URI from argv[0]. If argv[0] @@ -95,14 +97,15 @@ <refsect1> <title>VERSION</title> - <para>This man page is correct for version 2.2 of the Samba suite.</para> + <para>This man page is correct for version 2.2 of + the Samba suite.</para> </refsect1> <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>.</para> + <para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + and <ulink url="samba.7.html">samba(7)</ulink>. + </para> </refsect1> <refsect1> @@ -118,11 +121,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbstatus.1.sgml b/docs/docbook/manpages/smbstatus.1.sgml index 67d39f2586..99963a4bec 100644 --- a/docs/docbook/manpages/smbstatus.1.sgml +++ b/docs/docbook/manpages/smbstatus.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbstatus.1"> +<refentry id="smbstatus"> <refmeta> <refentrytitle>smbstatus</refentrytitle> @@ -31,8 +31,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>smbstatus</command> is a very simple program to list the current Samba connections.</para> @@ -84,8 +84,8 @@ <varlistentry> <term>-p|--processes</term> - <listitem><para>print a list of <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> processes and exit. + <listitem><para>print a list of <ulink url="smbd.8.html"> + <command>smbd(8)</command></ulink> processes and exit. Useful for scripting.</para></listitem> </varlistentry> @@ -102,9 +102,9 @@ <term>-s|--conf=<configuration file></term> <listitem><para>The default configuration file name is determined at compile time. The file specified contains the - configuration details required by the server. See <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> for more information.</para> + configuration details required by the server. See <ulink + url="smb.conf.5.html"><filename>smb.conf(5)</filename> + </ulink> for more information.</para> </listitem> </varlistentry> @@ -128,9 +128,8 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> + <para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink> and + <ulink url="smb.conf.5.html">smb.conf(5)</ulink>.</para> </refsect1> <refsect1> @@ -143,11 +142,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbtar.1.sgml b/docs/docbook/manpages/smbtar.1.sgml index ffb5087347..bd70493b6b 100644 --- a/docs/docbook/manpages/smbtar.1.sgml +++ b/docs/docbook/manpages/smbtar.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbtar.1"> +<refentry id="smbtar"> <refmeta> <refentrytitle>smbtar</refentrytitle> @@ -37,12 +37,12 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>smbtar</command> is a very small shell script on top - of <citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry> which dumps SMB shares directly to tape.</para> + of <ulink url="smbclient.1.html"><command>smbclient(1)</command></ulink> + which dumps SMB shares directly to tape. </para> </refsect1> <refsect1> @@ -144,9 +144,8 @@ <varlistentry> <term>-l log level</term> <listitem><para>Log (debug) level. Corresponds to the - <parameter>-d</parameter> flag of <citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry>.</para></listitem> + <parameter>-d</parameter> flag of <command>smbclient(1) + </command>. </para></listitem> </varlistentry> </variablelist> </refsect1> @@ -182,9 +181,9 @@ <refsect1> <title>DIAGNOSTICS</title> - <para>See the <emphasis>DIAGNOSTICS</emphasis> section for the <citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry> command.</para> + <para>See the <emphasis>DIAGNOSTICS</emphasis> section for the + <ulink url="smbclient.1.html"><command>smbclient(1)</command> + </ulink> command.</para> </refsect1> @@ -197,11 +196,10 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> + <para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="smbclient.1.html"><command>smbclient(1)</command></ulink>, + <ulink url="smb.conf.5.html">smb.conf(5)</ulink>, + </para> </refsect1> <refsect1> @@ -218,11 +216,11 @@ url="mailto:Martin.Kraemer@mch.sni.de">Martin Kraemer</ulink>. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter.</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/smbumount.8.sgml b/docs/docbook/manpages/smbumount.8.sgml index 089ede79ea..d6a1b65b57 100644 --- a/docs/docbook/manpages/smbumount.8.sgml +++ b/docs/docbook/manpages/smbumount.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="smbumount.8"> +<refentry id="smbumount"> <refmeta> <refentrytitle>smbumount</refentrytitle> @@ -47,8 +47,8 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbmount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></para> + <para><ulink url="smbmount.8.html"><command>smbmount(8)</command> + </ulink></para> </refsect1> @@ -67,8 +67,7 @@ </para> <para>The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</para> + by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/swat.8.sgml b/docs/docbook/manpages/swat.8.sgml index 9c4daad6d0..c0052f3d53 100644 --- a/docs/docbook/manpages/swat.8.sgml +++ b/docs/docbook/manpages/swat.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="swat.8"> +<refentry id="swat"> <refmeta> <refentrytitle>swat</refentrytitle> @@ -23,13 +23,13 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>swat</command> allows a Samba administrator to - configure the complex <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file via a Web browser. In addition, + configure the complex <ulink url="smb.conf.5.html"><filename> + smb.conf(5)</filename></ulink> file via a Web browser. In addition, a <command>swat</command> configuration page has help links to all the configurable options in the <filename>smb.conf</filename> file allowing an administrator to easily look up the effects of any change. </para> @@ -46,9 +46,8 @@ <term>-s smb configuration file</term> <listitem><para>The default configuration file path is determined at compile time. The file specified contains - the configuration details required by the <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> server. This is the file - that <command>swat</command> will modify. + the configuration details required by the <command>smbd + </command> server. This is the file that <command>swat</command> will modify. 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. @@ -153,9 +152,8 @@ <varlistentry> <term><filename>/usr/local/samba/lib/smb.conf</filename></term> - <listitem><para>This is the default location of the <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> server configuration file that swat edits. Other + <listitem><para>This is the default location of the <filename>smb.conf(5) + </filename> server configuration file that swat edits. Other common places that systems install this file are <filename> /usr/samba/lib/smb.conf</filename> and <filename>/etc/smb.conf </filename>. This file describes all the services the server @@ -168,9 +166,8 @@ <refsect1> <title>WARNINGS</title> - <para><command>swat</command> will rewrite your <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file. It will rearrange the entries and delete all + <para><command>swat</command> will rewrite your <filename>smb.conf + </filename> file. It will rearrange the entries and delete all comments, <parameter>include=</parameter> and <parameter>copy= </parameter> options. If you have a carefully crafted <filename> smb.conf</filename> then back it up or don't use swat! </para> @@ -180,15 +177,16 @@ <refsect1> <title>VERSION</title> - <para>This man page is correct for version 2.2 of the Samba suite.</para> + <para>This man page is correct for version 2.2 of + the Samba suite.</para> </refsect1> <refsect1> <title>SEE ALSO</title> - <para><command>inetd(5)</command>, <citerefentry> - <refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></para> + <para><command>inetd(5)</command>, + <ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="smb.conf.5.html">smb.conf(5)</ulink> + </para> </refsect1> <refsect1> @@ -201,11 +199,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/testparm.1.sgml b/docs/docbook/manpages/testparm.1.sgml index ec8092a926..f34528a43d 100644 --- a/docs/docbook/manpages/testparm.1.sgml +++ b/docs/docbook/manpages/testparm.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="testparm.1"> +<refentry id="testparm"> <refmeta> <refentrytitle>testparm</refentrytitle> @@ -29,12 +29,11 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>testparm</command> is a very simple test program - to check an <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> configuration file for + to check an <command>smbd</command> configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that <command>smbd </command> will successfully load the configuration file.</para> @@ -83,9 +82,9 @@ <varlistentry> <term>-v</term> <listitem><para>If this option is specified, testparm - will also output all options that were not used in <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> and are thus set to their defaults.</para></listitem> + will also output all options that were not used in + <filename>smb.conf</filename> and are thus set to + their defaults.</para></listitem> </varlistentry> <varlistentry> @@ -99,8 +98,7 @@ <term>configfilename</term> <listitem><para>This is the name of the configuration file to check. If this parameter is not present then the - default <citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file will be checked. + default <filename>smb.conf</filename> file will be checked. </para></listitem> </varlistentry> @@ -110,9 +108,7 @@ <listitem><para>If this parameter and the following are specified, then <command>testparm</command> will examine the <parameter>hosts allow</parameter> and <parameter>hosts deny</parameter> - parameters in the <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file to + parameters in the <filename>smb.conf</filename> file to determine if the hostname with this IP address would be allowed access to the <command>smbd</command> server. If this parameter is supplied, the hostIP parameter must also @@ -134,11 +130,9 @@ <variablelist> <varlistentry> - <term><citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry></term> + <term><filename>smb.conf</filename></term> <listitem><para>This is usually the name of the configuration - file used by <citerefentry><refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry>. + file used by <command>smbd</command>. </para></listitem> </varlistentry> </variablelist> @@ -164,11 +158,9 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry>, <citerefentry> - <refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry></para> + <para><ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename></ulink>, + <ulink url="smbd.8.html"><command>smbd(8)</command></ulink> + </para> </refsect1> <refsect1> @@ -181,11 +173,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/testprns.1.sgml b/docs/docbook/manpages/testprns.1.sgml index 85cc860c4a..cd99494a9a 100644 --- a/docs/docbook/manpages/testprns.1.sgml +++ b/docs/docbook/manpages/testprns.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="testprns.1"> +<refentry id="testprns"> <refmeta> <refentrytitle>testprns</refentrytitle> @@ -23,13 +23,13 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>testprns</command> is a very simple test program to determine whether a given printer name is valid for use in - a service to be provided by <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>.</para> + a service to be provided by <ulink url="smbd.8.html"><command> + smbd(8)</command></ulink>. </para> <para>"Valid" in this context means "can be found in the printcap specified". This program is very stupid - so stupid in @@ -54,9 +54,8 @@ done beyond that required to extract the printer name. It may be that the print spooling system is more forgiving or less forgiving than <command>testprns</command>. However, if - <command>testprns</command> finds the printer then <citerefentry> - <refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry> should do so as well. </para></listitem> + <command>testprns</command> finds the printer then + <command>smbd</command> should do so as well. </para></listitem> </varlistentry> <varlistentry> @@ -118,9 +117,9 @@ <refsect1> <title>SEE ALSO</title> <para><filename>printcap(5)</filename>, - <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></para> + <ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="smbclient.1.html"><command>smbclient(1)</command></ulink> + </para> </refsect1> <refsect1> @@ -133,11 +132,11 @@ <para>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 <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> ftp://ftp.icce.rug.nl/pub/unix/</ulink>) 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.</para> + Samba 2.2 was done by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/vfstest.1.sgml b/docs/docbook/manpages/vfstest.1.sgml index c89035d814..d6c7e5f142 100644 --- a/docs/docbook/manpages/vfstest.1.sgml +++ b/docs/docbook/manpages/vfstest.1.sgml @@ -1,7 +1,8 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY % globalentities SYSTEM '../global.ent'> %globalentities; ]> -<refentry id="vfstest.1"> + +<refentry id="vfstest"> <refmeta> <refentrytitle>vfstest</refentrytitle> @@ -27,8 +28,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>vfstest</command> is a small command line utility that has the ability to test dso samba VFS modules. It gives the diff --git a/docs/docbook/manpages/wbinfo.1.sgml b/docs/docbook/manpages/wbinfo.1.sgml index 5003c847a4..a6ca244243 100644 --- a/docs/docbook/manpages/wbinfo.1.sgml +++ b/docs/docbook/manpages/wbinfo.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="wbinfo.1"> +<refentry id="wbinfo"> <refmeta> <refentrytitle>wbinfo</refentrytitle> @@ -37,15 +37,14 @@ <refsect1> <title>DESCRIPTION</title> - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This tool is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para>The <command>wbinfo</command> program queries and returns information - created and used by the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon. </para> + created and used by the <ulink url="winbindd.8.html"><command> + winbindd(8)</command></ulink> daemon. </para> - <para>The <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon must be configured + <para>The <command>winbindd(8)</command> daemon must be configured and running for the <command>wbinfo</command> program to be able to return information.</para> </refsect1> @@ -57,30 +56,27 @@ <varlistentry> <term>-u</term> <listitem><para>This option will list all users available - in the Windows NT domain for which the <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon is operating in. Users in all trusted domains + in the Windows NT domain for which the <command>winbindd(8) + </command> daemon is operating in. Users in all trusted domains will also be listed. Note that this operation does not assign - user ids to any users that have not already been seen by <citerefentry> - <refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum></citerefentry> - .</para></listitem> + user ids to any users that have not already been seen by + <command>winbindd(8)</command>.</para></listitem> </varlistentry> <varlistentry> <term>-g</term> <listitem><para>This option will list all groups available - in the Windows NT domain for which the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> daemon is operating in. Groups in all trusted domains + in the Windows NT domain for which the <command>winbindd(8) + </command> daemon is operating in. Groups in all trusted domains will also be listed. Note that this operation does not assign - group ids to any groups that have not already been - seen by <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>. </para></listitem> + group ids to any groups that have not already been seen by + <command>winbindd(8)</command>. </para></listitem> </varlistentry> <varlistentry> <term>-N name</term> <listitem><para>The <parameter>-N</parameter> option - queries <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to query the WINS + queries <command>winbindd(8)</command> to query the WINS server for the IP address associated with the NetBIOS name specified by the <parameter>name</parameter> parameter. </para></listitem> @@ -90,8 +86,7 @@ <varlistentry> <term>-I ip</term> <listitem><para>The <parameter>-I</parameter> option - queries <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to send a node status + queries <command>winbindd(8)</command> to send a node status request to get the NetBIOS name associated with the IP address specified by the <parameter>ip</parameter> parameter. </para></listitem> @@ -101,15 +96,13 @@ <varlistentry> <term>-n name</term> <listitem><para>The <parameter>-n</parameter> option - queries <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> for the SID + queries <command>winbindd(8)</command> for the SID associated with the name specified. Domain names can be specified before the user name by using the winbind separator character. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1. If no domain is specified then the - domain used is the one specified in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> <parameter>workgroup - </parameter> parameter. </para></listitem> + domain used is the one specified in the <filename>smb.conf</filename> + <parameter>workgroup</parameter> parameter. </para></listitem> </varlistentry> @@ -142,18 +135,16 @@ <varlistentry> <term>-S sid</term> <listitem><para>Convert a SID to a UNIX user id. If the SID - does not correspond to a UNIX user mapped by <citerefentry> - <refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry> then the operation will fail. </para></listitem> + does not correspond to a UNIX user mapped by <command> + winbindd(8)</command> then the operation will fail. </para></listitem> </varlistentry> <varlistentry> <term>-Y sid</term> <listitem><para>Convert a SID to a UNIX group id. If the SID - does not correspond to a UNIX group mapped by <citerefentry> - <refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum></citerefentry> then - the operation will fail. </para></listitem> + does not correspond to a UNIX group mapped by <command> + winbindd(8)</command> then the operation will fail. </para></listitem> </varlistentry> @@ -169,8 +160,7 @@ <varlistentry> <term>-m</term> <listitem><para>Produce a list of domains trusted by the - Windows NT server <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> contacts + Windows NT server <command>winbindd(8)</command> contacts when resolving names. This list does not include the Windows NT domain the server is a Primary Domain Controller for. </para></listitem> @@ -211,9 +201,8 @@ <title>EXIT STATUS</title> <para>The wbinfo program returns 0 if the operation - succeeded, or 1 if the operation failed. If the <citerefentry> - <refentrytitle>winbindd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry> daemon is not working <command>wbinfo</command> will always return + succeeded, or 1 if the operation failed. If the <command>winbindd(8) + </command> daemon is not working <command>wbinfo</command> will always return failure. </para> </refsect1> @@ -227,8 +216,8 @@ <refsect1> <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></para> + <para><ulink url="winbindd.8.html"><command>winbindd(8)</command> + </ulink></para> </refsect1> <refsect1> @@ -243,8 +232,7 @@ were written by Tim Potter.</para> <para>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.</para> + by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/manpages/winbindd.8.sgml b/docs/docbook/manpages/winbindd.8.sgml index a44e195d8c..ccef2fa623 100644 --- a/docs/docbook/manpages/winbindd.8.sgml +++ b/docs/docbook/manpages/winbindd.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="winbindd.8"> +<refentry id="winbindd"> <refmeta> <refentrytitle>winbindd</refentrytitle> @@ -29,8 +29,8 @@ <refsect1> <title>DESCRIPTION</title> - <para>This program is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> + <para>This program is part of the <ulink url="samba.7.html"> + Samba</ulink> suite.</para> <para><command>winbindd</command> is a daemon that provides a service for the Name Service Switch capability that is present @@ -88,11 +88,12 @@ <filename>/etc/nsswitch.conf</filename> file can be used to initially resolve user and group information from <filename>/etc/passwd </filename> and <filename>/etc/group</filename> and then from the - Windows NT server. -<programlisting> + Windows NT server. </para> + + <para><programlisting> passwd: files winbind group: files winbind -</programlisting></para> + </programlisting></para> <para>The following simple configuration in the <filename>/etc/nsswitch.conf</filename> file can be used to initially @@ -171,8 +172,7 @@ group: files winbind <varlistentry> <term>-s|--conf=smb.conf</term> <listitem><para>Specifies the location of the all-important - <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. </para></listitem> + <filename>smb.conf</filename> file. </para></listitem> </varlistentry> </variablelist> </refsect1> @@ -208,9 +208,8 @@ group: files winbind <title>CONFIGURATION</title> <para>Configuration of the <command>winbindd</command> daemon - is done through configuration parameters in the <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file. All parameters should be specified in the + is done through configuration parameters in the <filename>smb.conf(5) + </filename> file. All parameters should be specified in the [global] section of smb.conf. </para> <itemizedlist> @@ -244,24 +243,27 @@ group: files winbind following setup. This was tested on a RedHat 6.2 Linux box. </para> <para>In <filename>/etc/nsswitch.conf</filename> put the - following: -<programlisting> + following:</para> + + <para><programlisting> passwd: files winbind group: files winbind -</programlisting></para> + </programlisting></para> + + <para>In <filename>/etc/pam.d/*</filename> replace the + <parameter>auth</parameter> lines with something like this: </para> - <para>In <filename>/etc/pam.d/*</filename> replace the <parameter> - auth</parameter> lines with something like this: -<programlisting> + + <para><programlisting> auth required /lib/security/pam_securetty.so auth required /lib/security/pam_nologin.so auth sufficient /lib/security/pam_winbind.so auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok -</programlisting></para> + </programlisting></para> - <para>Note in particular the use of the <parameter>sufficient - </parameter> keyword and the <parameter>use_first_pass</parameter> keyword. </para> + <para>Note in particular the use of the <parameter>sufficient</parameter> + keyword and the <parameter>use_first_pass</parameter> keyword. </para> <para>Now replace the account lines with this: </para> @@ -271,24 +273,26 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok <para>The next step is to join the domain. To do that use the <command>smbpasswd</command> program like this: </para> - <para><command>net join -S PDC -U Administrator</command></para> + <para><command>smbpasswd -j DOMAIN -r PDC -U + Administrator</command></para> <para>The username after the <parameter>-U</parameter> can be any Domain user that has administrator privileges on the machine. - Substitute the name or IP of your PDC for "PDC".</para> + Substitute your domain name for "DOMAIN" and the name of your PDC + for "PDC".</para> <para>Next copy <filename>libnss_winbind.so</filename> to - <filename>/lib</filename> and <filename>pam_winbind.so - </filename> to <filename>/lib/security</filename>. A symbolic link needs to be + <filename>/lib</filename> and <filename>pam_winbind.so</filename> + to <filename>/lib/security</filename>. A symbolic link needs to be made from <filename>/lib/libnss_winbind.so</filename> to <filename>/lib/libnss_winbind.so.2</filename>. If you are using an older version of glibc then the target of the link should be <filename>/lib/libnss_winbind.so.1</filename>.</para> - <para>Finally, setup a <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> containing directives like the - following: -<programlisting> + <para>Finally, setup a <filename>smb.conf</filename> containing directives like the + following: </para> + + <para><programlisting> [global] winbind separator = + winbind cache time = 10 @@ -299,7 +303,7 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok workgroup = DOMAIN security = domain password server = * -</programlisting></para> + </programlisting></para> <para>Now start winbindd and you should find that your user and @@ -317,10 +321,9 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok <para>The following notes are useful when configuring and running <command>winbindd</command>: </para> - <para><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> must be running on the local machine - for <command>winbindd</command> to work. <command>winbindd</command> queries - the list of trusted domains for the Windows NT server + <para><command>nmbd</command> must be running on the local machine + for <command>winbindd</command> to work. <command>winbindd</command> + queries the list of trusted domains for the Windows NT server on startup and when a SIGHUP is received. Thus, for a running <command> winbindd</command> to become aware of new trust relationships between servers, it must be sent a SIGHUP signal. </para> @@ -354,9 +357,8 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok <variablelist> <varlistentry> <term>SIGHUP</term> - <listitem><para>Reload the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file and - apply any parameter changes to the running + <listitem><para>Reload the <filename>smb.conf(5)</filename> + file and apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted by winbindd is also reloaded. </para></listitem> @@ -429,13 +431,10 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok <refsect1> <title>SEE ALSO</title> - <para><filename>nsswitch.conf(5)</filename>, <citerefentry> - <refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>, <citerefentry> - <refentrytitle>wbinfo</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry> - <refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></para> + <para><filename>nsswitch.conf(5)</filename>, + <ulink url="samba.7.html">samba(7)</ulink>, + <ulink url="wbinfo.1.html">wbinfo(1)</ulink>, + <ulink url="smb.conf.5.html">smb.conf(5)</ulink></para> </refsect1> <refsect1> @@ -446,12 +445,11 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.</para> - <para><command>wbinfo</command> and <command>winbindd</command> were - written by Tim Potter.</para> + <para><command>wbinfo</command> and <command>winbindd</command> + were written by Tim Potter.</para> <para>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.</para> + by Gerald Carter</para> </refsect1> </refentry> diff --git a/docs/docbook/projdoc/ADS-HOWTO.sgml b/docs/docbook/projdoc/ADS-HOWTO.sgml index 887ecd74c2..3e34d53c0a 100644 --- a/docs/docbook/projdoc/ADS-HOWTO.sgml +++ b/docs/docbook/projdoc/ADS-HOWTO.sgml @@ -14,8 +14,7 @@ This is a rough guide to setting up Samba 3.0 with kerberos authentication again Windows2000 KDC. </para> -<para>Pieces you need before you begin:</para> -<para> +<para>Pieces you need before you begin: <simplelist> <member>a Windows 2000 server.</member> <member>samba 3.0 or higher.</member> @@ -27,8 +26,7 @@ Windows2000 KDC. <sect1> <title>Installing the required packages for Debian</title> -<para>On Debian you need to install the following packages:</para> -<para> +<para>On Debian you need to install the following packages: <simplelist> <member>libkrb5-dev</member> <member>krb5-user</member> @@ -39,8 +37,7 @@ Windows2000 KDC. <sect1> <title>Installing the required packages for RedHat</title> -<para>On RedHat this means you should have at least: </para> -<para> +<para>On RedHat this means you should have at least: <simplelist> <member>krb5-workstation (for kinit)</member> <member>krb5-libs (for linking with)</member> @@ -60,8 +57,7 @@ to get them off CD2.</para> <para>If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.</para> -<para>After you run configure make sure that include/config.h it - generates contains +<para>After you run configure make sure that include/config.h contains lines like this:</para> <para><programlisting> @@ -90,10 +86,9 @@ In case samba can't figure out your ads server using your realm name, use the </programlisting> </para> -<para>You do *not* need a smbpasswd file, and older clients will - be authenticated as if "security = domain", although it won't do any harm - and allows you to have local users not in the domain. - I expect that the above +<para>You do *not* need a smbpasswd file, although it won't do any harm + and if you have one then Samba will be able to fall back to normal + password security for older clients. I expect that the above required options will change soon when we get better active directory integration.</para> </sect1> @@ -104,7 +99,7 @@ In case samba can't figure out your ads server using your realm name, use the <para>The minimal configuration for krb5.conf is:</para> <para><programlisting> -[realms] + [realms] YOUR.KERBEROS.REALM = { kdc = your.kerberos.server } @@ -133,7 +128,7 @@ to join the realm. <para> If all you want is kerberos support in smbclient then you can skip straight to step 5 now. Step 3 is only needed if you want kerberos -support for smbd and winbindd. +support in smbd. </para> </sect1> @@ -142,7 +137,9 @@ support for smbd and winbindd. <title>Create the computer account</title> <para> -As a user that has write permission on the Samba private directory +Do a "kinit" as a user that has authority to change arbitrary +passwords on the KDC ("Administrator" is a good choice). Then as a +user that has write permission on the Samba private directory (usually root) run: <command>net ads join</command> </para> @@ -152,6 +149,8 @@ As a user that has write permission on the Samba private directory <para> <variablelist> +<varlistentry><term>"bash: kinit: command not found"</term> +<listitem><para>kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)</para></listitem></varlistentry> <varlistentry><term>"ADS support not compiled in"</term> <listitem><para>Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the kerberos libs and headers are installed.</para></listitem></varlistentry> </variablelist> diff --git a/docs/docbook/projdoc/Browsing-Quickguide.sgml b/docs/docbook/projdoc/Browsing-Quickguide.sgml index 0a5cf72038..8ecc795966 100644 --- a/docs/docbook/projdoc/Browsing-Quickguide.sgml +++ b/docs/docbook/projdoc/Browsing-Quickguide.sgml @@ -1,10 +1,9 @@ <chapter id="Browsing-Quick"> <chapterinfo> <author> - <firstname>John H</firstname><surname>Terpstra</surname> + <firstname>John</firstname><surname>Terpstra</surname> </author> <pubdate>July 5, 1998</pubdate> - <pubdate>Updated: March 15, 2003</pubdate> </chapterinfo> <title>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</title> @@ -17,22 +16,16 @@ of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling except by way of name to address mapping. </para> -<para> -Note: MS Windows 2000 and later can be configured to operate with NO NetBIOS -over TCP/IP. Samba-3 and later also supports this mode of operation. -</para> - - <sect1> <title>Discussion</title> <para> Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. -MS Windows products can do likewise. NetBIOS based networking uses broadcast -messaging to affect browse list management. When running NetBIOS over -TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast. +Block) based messaging. SMB messaging is implemented using NetBIOS. Samba +implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can +do likewise. NetBIOS based networking uses broadcast messaging to affect +browse list management. When running NetBIOS over TCP/IP this uses UDP +based messaging. UDP messages can be broadcast or unicast. </para> <para> @@ -52,27 +45,20 @@ the "remote browse sync" parameters to your smb.conf file. </para> <para> -If only one WINS server is used for an entire multi-segment network then -the use of the "remote announce" and the "remote browse sync" parameters -should NOT be necessary. -</para> - -<para> -As of Samba-3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation. +If only one WINS server is used then the use of the "remote announce" and the +"remote browse sync" parameters should NOT be necessary. </para> <para> -Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one nmbd configured -as a WINS server on the network. Some sites have used multiple Samba WINS -servers for redundancy (one server per subnet) and then used "remote browse -sync" and "remote announce" to affect browse list collation across all -segments. Note that this means clients will only resolve local names, -and must be configured to use DNS to resolve names on other subnets in -order to resolve the IP addresses of the servers they can see on other -subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie: an 'if all else fails' scenario). +Samba WINS does not support MS-WINS replication. This means that when setting up +Samba as a WINS server there must only be one nmbd configured as a WINS server +on the network. Some sites have used multiple Samba WINS servers for redundancy +(one server per subnet) and then used "remote browse sync" and "remote announce" +to affect browse list collation across all segments. Note that this means +clients will only resolve local names, and must be configured to use DNS to +resolve names on other subnets in order to resolve the IP addresses of the +servers they can see on other subnets. This setup is not recommended, but is +mentioned as a practical consideration (ie: an 'if all else fails' scenario). </para> <para> @@ -140,9 +126,8 @@ simultaneously the LMB on it's network segment. <para> The syntax of the "remote browse sync" parameter is: - <programlisting> -remote browse sync = a.b.c.d + remote browse sync = a.b.c.d </programlisting> where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment. @@ -212,9 +197,8 @@ To configure Samba to register with a WINS server just add </para> <para> -<emphasis>DO NOT EVER</emphasis> use both "wins support = yes" together -with "wins server = a.b.c.d" particularly not using it's own IP address. -Specifying both will cause nmbd to refuse to start! +<emphasis>DO NOT EVER</emphasis> use both "wins support = yes" together with "wins server = a.b.c.d" +particularly not using it's own IP address. </para> </sect1> @@ -228,7 +212,7 @@ one protocol on an MS Windows machine. </para> <para> -Every NetBIOS machine takes part in a process of electing the LMB (and DMB) +Every NetBIOS machine take part in a process of electing the LMB (and DMB) every 15 minutes. A set of election criteria is used to determine the order of precidence for winning this election process. A machine running Samba or Windows NT will be biased so that the most suitable machine will predictably @@ -247,15 +231,6 @@ as an LMB and thus browse list operation on all TCP/IP only machines will fail. </para> -<para><emphasis> -Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols. -</emphasis></para> - <para> The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! </para> @@ -268,35 +243,36 @@ The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! <para> Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information -are:</para> - +are: <simplelist> <member>WINS: the best tool!</member> <member>LMHOSTS: is static and hard to maintain.</member> <member>Broadcast: uses UDP and can not resolve names across remote segments.</member> </simplelist> +</para> <para> -Alternative means of name resolution includes:</para> +Alternative means of name resolution includes: <simplelist> <member>/etc/hosts: is static, hard to maintain, and lacks name_type info</member> <member>DNS: is a good choice but lacks essential name_type info.</member> </simplelist> +</para> <para> Many sites want to restrict DNS lookups and want to avoid broadcast name resolution traffic. The "name resolve order" parameter is of great help here. The syntax of the "name resolve order" parameter is: <programlisting> -name resolve order = wins lmhosts bcast host + name resolve order = wins lmhosts bcast host </programlisting> _or_ <programlisting> -name resolve order = wins lmhosts (eliminates bcast and host) + name resolve order = wins lmhosts (eliminates bcast and host) </programlisting> The default is: <programlisting> -name resolve order = host lmhost wins bcast + name resolve order = host lmhost wins bcast </programlisting>. where "host" refers the the native methods used by the Unix system to implement the gethostbyname() function call. This is normally diff --git a/docs/docbook/projdoc/Browsing.sgml b/docs/docbook/projdoc/Browsing.sgml index aeb3b477c5..13d6fce917 100644 --- a/docs/docbook/projdoc/Browsing.sgml +++ b/docs/docbook/projdoc/Browsing.sgml @@ -27,15 +27,8 @@ document. </para> <para> -MS Windows 2000 and later, as with Samba-3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly. -</para> - -<para> -Where NetBIOS over TCP/IP is enabled use of a WINS server is highly +Browsing will NOT work if name resolution from NetBIOS names to IP +addresses does not function correctly. Use of a WINS server is highly recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. WINS allows remote segment clients to obtain NetBIOS name_type information that can NOT be provided by any other means of name resolution. @@ -47,10 +40,14 @@ that can NOT be provided by any other means of name resolution. <title>Browsing support in samba</title> <para> -Samba facilitates browsing. The browsing is supported by nmbd +Samba now fully supports browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file (see smb.conf(5)). +</para> + +<para> Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available. +for samba to support domain logons and scripts is now available. See +DOMAIN.txt for more information on domain logons. </para> <para> @@ -71,12 +68,12 @@ that is providing this service. <para> [Note that nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server. +necessary to specifically use samba as your WINS server. NTAS can +be configured as your WINS server. In a mixed NT server and +samba environment on a Wide Area Network, it is recommended that +you use the NT server's WINS server capabilities. In a samba-only +environment, it is recommended that you use one and only one nmbd +as your WINS server]. </para> <para> @@ -116,15 +113,6 @@ connection that lists the shares is done as guest, and thus you must have a valid guest account. </para> -<para><emphasis> -MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources. -</emphasis></para> - <para> Also, a lot of people are getting bitten by the problem of too many parameters on the command line of nmbd in inetd.conf. This trick is to @@ -144,7 +132,7 @@ in smb.conf) <sect1> <title>Browsing across subnets</title> <para> -Since the release of Samba 1.9.17(alpha1) Samba has been +With the release of Samba 1.9.17(alpha1 and above) Samba has been updated to enable it to support the replication of browse lists across subnet boundaries. New code and options have been added to achieve this. This section describes how to set this feature up @@ -179,7 +167,8 @@ settings) for Samba this is in the smb.conf file. Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. -Samba is capable of cross subnet browsing when configured correctly. +However, with the 1.9.17 release, Samba is capable of cross subnet +browsing when configured correctly. </para> <para> @@ -430,9 +419,9 @@ in the [globals] section add the line </para> <para> -Versions of Samba prior to 1.9.17 had this parameter default to +Versions of Samba previous to 1.9.17 had this parameter default to yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to a recent version, or at the very +strongly suggested you upgrade to 1.9.17 or above, or at the very least set the parameter to 'no' on all these machines. </para> @@ -484,7 +473,7 @@ machine or its IP address. Note that this line MUST NOT BE SET in the smb.conf file of the Samba server acting as the WINS server itself. If you set both the "<command>wins support = yes</command>" option and the -"<command>wins server = <name></command>" option then +"<command>wins server = >name<</command>" option then nmbd will fail to start. </para> @@ -549,12 +538,11 @@ server, if you require. <para> Next, you should ensure that each of the subnets contains a machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -to use these). To make a Samba server a local master browser -set the following options in the [global] section of the -smb.conf file : +workgroup. Any NT machine should be able to do this, as will +Windows 95 machines (although these tend to get rebooted more +often, so it's not such a good idea to use these). To make a +Samba server a local master browser set the following +options in the [global] section of the smb.conf file : </para> <para> @@ -606,7 +594,7 @@ you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a Domain name is also the Domain master browser for that name, and many things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN<1B>) with WINS instead of the PDC. +browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC. </para> <para> @@ -673,8 +661,8 @@ samba systems!) </para> <para> -A "os level" of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32. +A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A +NTAS domain controller uses level 32. </para> <para>The maximum os level is 255</para> diff --git a/docs/docbook/projdoc/CVS-Access.sgml b/docs/docbook/projdoc/CVS-Access.sgml new file mode 100644 index 0000000000..98ef925f20 --- /dev/null +++ b/docs/docbook/projdoc/CVS-Access.sgml @@ -0,0 +1,157 @@ +<chapter id="cvs-access"> + + +<chapterinfo> + <author> + <affiliation> + <orgname>Samba Team</orgname> + </affiliation> + </author> + + + <pubdate> (22 May 2001) </pubdate> +</chapterinfo> + +<title>HOWTO Access Samba source code via CVS</title> + +<sect1> +<title>Introduction</title> + +<para> +Samba is developed in an open environment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymous CVS using the instructions +detailed in this chapter. +</para> + +<para> +This document is a modified version of the instructions found at +<ulink url="http://samba.org/samba/cvs.html">http://samba.org/samba/cvs.html</ulink> +</para> + +</sect1> + + +<sect1> +<title>CVS Access to samba.org</title> + +<para> +The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host. +</para> + +<sect2> +<title>Access via CVSweb</title> + +<para> +You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository. +</para> + +<para> +Use the URL : <ulink +url="http://samba.org/cgi-bin/cvsweb">http://samba.org/cgi-bin/cvsweb</ulink> +</para> +</sect2> + +<sect2> +<title>Access via cvs</title> + +<para> +You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them up to date via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser. +</para> + +<para> +To download the latest cvs source code, point your +browser at the URL : <ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com. +</para> + +<para> +To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name +</para> + +<orderedlist> +<listitem> + <para> + Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + </para> +</listitem> + + +<listitem> + <para> + Run the command + </para> + + <para> + <command>cvs -d :pserver:cvs@samba.org:/cvsroot login</command> + </para> + + <para> + When it asks you for a password type <userinput>cvs</userinput>. + </para> +</listitem> + + +<listitem> + <para> + Run the command + </para> + + <para> + <command>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</command> + </para> + + <para> + This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + </para> + + <para> + CVS branches other HEAD can be obtained by using the <parameter>-r</parameter> + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. + </para> + + <para> + <command>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</command> + </para> +</listitem> + +<listitem> + <para> + Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + </para> + + <para> + <command>cvs update -d -P</command> + </para> +</listitem> +</orderedlist> + +</sect2> +</sect1> + +</chapter> diff --git a/docs/docbook/projdoc/DOMAIN_MEMBER.sgml b/docs/docbook/projdoc/DOMAIN_MEMBER.sgml index b178bfd2c2..8a30a5527d 100644 --- a/docs/docbook/projdoc/DOMAIN_MEMBER.sgml +++ b/docs/docbook/projdoc/DOMAIN_MEMBER.sgml @@ -25,29 +25,79 @@ </chapterinfo> -<title>Samba as a NT4 or Win2k domain member</title> +<title>Samba as a NT4 domain member</title> <sect1> - <title>Joining an NT Domain with Samba 3.0</title> + <title>Joining an NT Domain with Samba 2.2</title> - <para>Assume you have a Samba 3.0 server with a NetBIOS name of - <constant>SERV1</constant> and are joining an or Win2k NT domain called + <para>Assume you have a Samba 2.x server with a NetBIOS name of + <constant>SERV1</constant> and are joining an NT domain called <constant>DOM</constant>, which has a PDC with a NetBIOS name of <constant>DOMPDC</constant> and two backup domain controllers with NetBIOS names <constant>DOMBDC1</constant> and <constant>DOMBDC2 </constant>.</para> - <para>Firstly, you must edit your <ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename> + <para>In order to join the domain, first stop all Samba daemons + and run the command:</para> + + <para><prompt>root# </prompt><userinput>smbpasswd -j DOM -r DOMPDC + -U<replaceable>Administrator%password</replaceable></userinput></para> + + <para>as we are joining the domain DOM and the PDC for that domain + (the only machine that has write access to the domain SAM database) + is DOMPDC. The <replaceable>Administrator%password</replaceable> is + the login name and password for an account which has the necessary + privilege to add machines to the domain. If this is successful + you will see the message:</para> + + <para><computeroutput>smbpasswd: Joined domain DOM.</computeroutput> + </para> + + <para>in your terminal window. See the <ulink url="smbpasswd.8.html"> + smbpasswd(8)</ulink> man page for more details.</para> + + <para>There is existing development code to join a domain + without having to create the machine trust account on the PDC + beforehand. This code will hopefully be available soon + in release branches as well.</para> + + <para>This command goes through the machine account password + change protocol, then writes the new (random) machine account + password for this Samba server into a file in the same directory + in which an smbpasswd file would be stored - normally :</para> + + <para><filename>/usr/local/samba/private</filename></para> + + <para>In Samba 2.0.x, the filename looks like this:</para> + + <para><filename><replaceable><NT DOMAIN NAME></replaceable>.<replaceable><Samba + Server Name></replaceable>.mac</filename></para> + + <para>The <filename>.mac</filename> suffix stands for machine account + password file. So in our example above, the file would be called:</para> + + <para><filename>DOM.SERV1.mac</filename></para> + + <para>In Samba 2.2, this file has been replaced with a TDB + (Trivial Database) file named <filename>secrets.tdb</filename>. + </para> + + + <para>This file is created and owned by root and is not + readable by any other user. It is the key to the domain-level + security for your system, and should be treated as carefully + as a shadow password file.</para> + + <para>Now, before restarting the Samba daemons you must + edit your <ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename> </ulink> file to tell Samba it should now use domain security.</para> <para>Change (or add) your <ulink url="smb.conf.5.html#SECURITY"> <parameter>security =</parameter></ulink> line in the [global] section of your smb.conf to read:</para> - <para><command>security = domain</command> or - <command>security = ads</command> depending on if the PDC is - NT4 or running Active Directory respectivly.</para> + <para><command>security = domain</command></para> <para>Next change the <ulink url="smb.conf.5.html#WORKGROUP"><parameter> workgroup =</parameter></ulink> line in the [global] section to read: </para> @@ -78,47 +128,11 @@ <para><command>password server = *</command></para> - <para>This method, allows Samba to use exactly the same - mechanism that NT does. This + <para>This method, which was introduced in Samba 2.0.6, + allows Samba to use exactly the same mechanism that NT does. This method either broadcasts or uses a WINS database in order to find domain controllers to authenticate against.</para> - <para>In order to actually join the domain, you must run this - command:</para> - - <para><prompt>root# </prompt><userinput>net join -S DOMPDC - -U<replaceable>Administrator%password</replaceable></userinput></para> - - <para>as we are joining the domain DOM and the PDC for that domain - (the only machine that has write access to the domain SAM database) - is DOMPDC. The <replaceable>Administrator%password</replaceable> is - the login name and password for an account which has the necessary - privilege to add machines to the domain. If this is successful - you will see the message:</para> - - <para><computeroutput>Joined domain DOM.</computeroutput> - or <computeroutput>Joined 'SERV1' to realm 'MYREALM'</computeroutput> - </para> - - <para>in your terminal window. See the <ulink url="net.8.html"> - net(8)</ulink> man page for more details.</para> - - <para>This process joins the server to thedomain - without having to create the machine trust account on the PDC - beforehand.</para> - - <para>This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :</para> - - <para><filename>/usr/local/samba/private/secrets.tdb</filename></para> - - <para>This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file.</para> - <para>Finally, restart your Samba daemons and get ready for clients to begin using domain security!</para> </sect1> @@ -130,8 +144,23 @@ <para> Many people have asked regarding the state of Samba's ability to participate in a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows -2000 domain operating in mixed or native mode. The steps above apply -to both NT4 and Windows 2000. +2000 domain operating in mixed or native mode. +</para> + +<para> +There is much confusion between the circumstances that require a "mixed" mode +Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode +Win2k domain controller is only needed if Windows NT BDCs must exist in the same +domain. By default, a Win2k DC in "native" mode will still support +NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and +NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server. +</para> + +<para> +The steps for adding a Samba 2.2 host to a Win2k domain are the same as those +for adding a Samba server to a Windows NT 4.0 domain. The only exception is that +the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and +Computers" MMC (Microsoft Management Console) plugin. </para> </sect1> @@ -176,7 +205,13 @@ to both NT4 and Windows 2000. <para>And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc. </para> + as the user SID, the list of NT groups the user belongs to, etc. All + this information will allow Samba to be extended in the future into + a mode the developers currently call appliance mode. In this mode, + no local Unix users will be necessary, and Samba will generate Unix + uids and gids from the information passed back from the PDC when a + user is authenticated, making a Samba server truly plug and play + in an NT domain environment. Watch for this code soon.</para> <para><emphasis>NOTE:</emphasis> Much of the text of this document was first published in the Web magazine <ulink url="http://www.linuxworld.com"> diff --git a/docs/docbook/projdoc/Diagnosis.sgml b/docs/docbook/projdoc/Diagnosis.sgml index 1e2e6d7598..8c1b784433 100644 --- a/docs/docbook/projdoc/Diagnosis.sgml +++ b/docs/docbook/projdoc/Diagnosis.sgml @@ -17,7 +17,7 @@ <pubdate>Wed Jan 15</pubdate> </chapterinfo> -<title>The samba checklist</title> +<title>Diagnosing your samba server</title> <sect1> <title>Introduction</title> diff --git a/docs/docbook/projdoc/ENCRYPTION.sgml b/docs/docbook/projdoc/ENCRYPTION.sgml new file mode 100644 index 0000000000..f903d7d334 --- /dev/null +++ b/docs/docbook/projdoc/ENCRYPTION.sgml @@ -0,0 +1,189 @@ +<chapter id="pwencrypt"> + + +<chapterinfo> + <author> + <firstname>Jeremy</firstname><surname>Allison</surname> + <affiliation> + <orgname>Samba Team</orgname> + <address> + <email>jra@samba.org</email> + </address> + </affiliation> + </author> + + <author> + <firstname>Jelmer</firstname><surname>Vernooij</surname> + <affiliation> + <orgname>Samba Team</orgname> + <address> + <email>jelmer@samba.org</email> + </address> + </affiliation> + </author> + + <pubdate>4 November 2002</pubdate> +</chapterinfo> + +<title>LanMan and NT Password Encryption in Samba</title> + + +<sect1> + <title>Introduction</title> + + <para>Newer windows clients send encrypted passwords over + the wire, instead of plain text passwords. The newest clients + will only send encrypted passwords and refuse to send plain text + passwords, unless their registry is tweaked.</para> + + <para>These passwords can't be converted to unix style encrypted + passwords. Because of that you can't use the standard unix + user database, and you have to store the Lanman and NT hashes + somewhere else. For more information, see the documentation + about the <command>passdb backend = </command> parameter. + </para> + +</sect1> + +<sect1> + <title>Important Notes About Security</title> + + <para>The unix and SMB password encryption techniques seem similar + on the surface. This similarity is, however, only skin deep. The unix + scheme typically sends clear text passwords over the network when + logging in. This is bad. The SMB encryption scheme never sends the + cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed + values are a "password equivalent". You cannot derive the user's + password from them, but they could potentially be used in a modified + client to gain access to a server. This would require considerable + technical knowledge on behalf of the attacker but is perfectly possible. + You should thus treat the smbpasswd file as though it contained the + cleartext passwords of all your users. Its contents must be kept + secret, and the file should be protected accordingly.</para> + + <para>Ideally we would like a password scheme which neither requires + plain text passwords on the net or on disk. Unfortunately this + is not available as Samba is stuck with being compatible with + other SMB systems (WinNT, WfWg, Win95 etc). </para> + + <warning> + <para>Note that Windows NT 4.0 Service pack 3 changed the + default for permissible authentication so that plaintext + passwords are <emphasis>never</emphasis> sent over the wire. + The solution to this is either to switch to encrypted passwords + with Samba or edit the Windows NT registry to re-enable plaintext + passwords. See the document WinNT.txt for details on how to do + this.</para> + + <para>Other Microsoft operating systems which also exhibit + this behavior includes</para> + + <itemizedlist> + <listitem><para>MS DOS Network client 3.0 with + the basic network redirector installed</para></listitem> + + <listitem><para>Windows 95 with the network redirector + update installed</para></listitem> + + <listitem><para>Windows 98 [se]</para></listitem> + + <listitem><para>Windows 2000</para></listitem> + </itemizedlist> + + <para><emphasis>Note :</emphasis>All current release of + Microsoft SMB/CIFS clients support authentication via the + SMB Challenge/Response mechanism described here. Enabling + clear text authentication does not disable the ability + of the client to participate in encrypted authentication.</para> + </warning> + + <sect2> + <title>Advantages of SMB Encryption</title> + + <itemizedlist> + <listitem><para>plain text passwords are not passed across + the network. Someone using a network sniffer cannot just + record passwords going to the SMB server.</para> + </listitem> + + <listitem><para>WinNT doesn't like talking to a server + that isn't using SMB encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. + </para></listitem> + </itemizedlist> + </sect2> + + + <sect2> + <title>Advantages of non-encrypted passwords</title> + + <itemizedlist> + <listitem><para>plain text passwords are not kept + on disk. </para></listitem> + + <listitem><para>uses same password file as other unix + services such as login and ftp</para></listitem> + + <listitem><para>you are probably already using other + services (such as telnet and ftp) which send plain text + passwords over the net, so sending them for SMB isn't + such a big deal.</para></listitem> + </itemizedlist> + </sect2> +</sect1> + + +<sect1> + <title>The smbpasswd Command</title> + + <para>The smbpasswd command maintains the two 32 byte password fields + in the smbpasswd file. If you wish to make it similar to the unix + <command>passwd</command> or <command>yppasswd</command> programs, + install it in <filename>/usr/local/samba/bin/</filename> (or your + main Samba binary directory).</para> + + <para><command>smbpasswd</command> now works in a client-server mode + where it contacts the local smbd to change the user's password on its + behalf. This has enormous benefits - as follows.</para> + + <para><command>smbpasswd</command> now has the capability + to change passwords on Windows NT servers (this only works when + the request is sent to the NT Primary Domain Controller if you + are changing an NT Domain user's password).</para> + + <para>To run smbpasswd as a normal user just type :</para> + + <para><prompt>$ </prompt><userinput>smbpasswd</userinput></para> + <para><prompt>Old SMB password: </prompt><userinput><type old value here - + or hit return if there was no old password></userinput></para> + <para><prompt>New SMB Password: </prompt><userinput><type new value> + </userinput></para> + <para><prompt>Repeat New SMB Password: </prompt><userinput><re-type new value + </userinput></para> + + <para>If the old value does not match the current value stored for + that user, or the two new values do not match each other, then the + password will not be changed.</para> + + <para>If invoked by an ordinary user it will only allow the user + to change his or her own Samba password.</para> + + <para>If run by the root user smbpasswd may take an optional + argument, specifying the user name whose SMB password you wish to + change. Note that when run as root smbpasswd does not prompt for + or check the old password value, thus allowing root to set passwords + for users who have forgotten their passwords.</para> + + <para><command>smbpasswd</command> is designed to work in the same way + and be familiar to UNIX users who use the <command>passwd</command> or + <command>yppasswd</command> commands.</para> + + <para>For more details on using <command>smbpasswd</command> refer + to the man page which will always be the definitive reference.</para> +</sect1> + +</chapter> diff --git a/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml b/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml index 06c1d3a87e..6d5a019fcb 100644 --- a/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml +++ b/docs/docbook/projdoc/GROUP-MAPPING-HOWTO.sgml @@ -1,4 +1,3 @@ -<?xml version="1.0" encoding="iso8859-1"?> <chapter id="groupmapping"> <chapterinfo> <author> diff --git a/docs/docbook/projdoc/Integrating-with-Windows.sgml b/docs/docbook/projdoc/Integrating-with-Windows.sgml index a4e79fd42b..3b0faf81af 100644 --- a/docs/docbook/projdoc/Integrating-with-Windows.sgml +++ b/docs/docbook/projdoc/Integrating-with-Windows.sgml @@ -295,16 +295,16 @@ The following are typical NetBIOS name/service type registrations: <para><programlisting> Unique NetBIOS Names: - MACHINENAME<00> = Server Service is running on MACHINENAME - MACHINENAME<03> = Generic Machine Name (NetBIOS name) - MACHINENAME<20> = LanMan Server service is running on MACHINENAME - WORKGROUP<1b> = Domain Master Browser + MACHINENAME<00> = Server Service is running on MACHINENAME + MACHINENAME<03> = Generic Machine Name (NetBIOS name) + MACHINENAME<20> = LanMan Server service is running on MACHINENAME + WORKGROUP<1b> = Domain Master Browser Group Names: - WORKGROUP<03> = Generic Name registered by all members of WORKGROUP - WORKGROUP<1c> = Domain Controllers / Netlogon Servers - WORKGROUP<1d> = Local Master Browsers - WORKGROUP<1e> = Internet Name Resolvers + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers </programlisting></para> <para> @@ -323,7 +323,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services. </para> diff --git a/docs/docbook/projdoc/NT_Security.sgml b/docs/docbook/projdoc/NT_Security.sgml index 2843331519..2259dae029 100644 --- a/docs/docbook/projdoc/NT_Security.sgml +++ b/docs/docbook/projdoc/NT_Security.sgml @@ -31,6 +31,12 @@ the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba administrator can set.</para> + + <para>In Samba 2.0.4 and above the default value of the + parameter <ulink url="smb.conf.5.html#NTACLSUPPORT"><parameter> + nt acl support</parameter></ulink> has been changed from + <constant>false</constant> to <constant>true</constant>, so + manipulation of permissions is turned on by default.</para> </sect1> <sect1> diff --git a/docs/docbook/projdoc/Other-Clients.sgml b/docs/docbook/projdoc/Other-Clients.sgml index 6ba04b01d3..f790024c3a 100644 --- a/docs/docbook/projdoc/Other-Clients.sgml +++ b/docs/docbook/projdoc/Other-Clients.sgml @@ -233,16 +233,6 @@ for use with <command>security = user</command> </sect2> -<sect2> -<title>Use TCP/IP as default protocol</title> - -<para>To support print queue reporting you may find -that you have to use TCP/IP as the default protocol under -WfWg. For some reason if you leave Netbeui as the default -it may break the print queue reporting on some systems. -It is presumably a WfWg bug.</para> - -</sect2> </sect1> <sect1> diff --git a/docs/docbook/projdoc/Portability.sgml b/docs/docbook/projdoc/Portability.sgml index dae267e8b5..afafacc5e4 100644 --- a/docs/docbook/projdoc/Portability.sgml +++ b/docs/docbook/projdoc/Portability.sgml @@ -175,16 +175,4 @@ Corrective Action: Delete the entry after the word loopback in the line starting 127.0.0.1 </para> </sect1> - -<sect1> -<title>AIX</title> -<sect2> -<title>Sequential Read Ahead</title> -<!-- From an email by William Jojo <jojowil@hvcc.edu> --> -<para> -Disabling Sequential Read Ahead using "vmtune -r 0" improves -samba performance significally. -</para> -</sect2> -</sect1> </chapter> diff --git a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml index e3bee32db0..7653e3d1c0 100644 --- a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml @@ -128,7 +128,7 @@ the password change is done. <sect1> -<title>Can Samba be a Backup Domain Controller to an NT PDC?</title> +<title>Can Samba be a Backup Domain Controller?</title> <para> With version 2.2, no. The native NT SAM replication protocols have @@ -138,12 +138,6 @@ been finished for version 2.2. </para> <para> -With version 3.0, the work on both the replication protocols and a -suitable storage mechanism has progressed, and some form of NT4 BDC -support is expected soon. -</para> - -<para> Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to @@ -184,8 +178,7 @@ whenever changes are made, or the PDC is set up as a NIS master server and the BDC as a NIS slave server. To set up the BDC as a mere NIS client would not be enough, as the BDC would not be able to access its user database in case of a PDC failure. -</para> -</listitem> +</para></listitem> <listitem><para> The Samba password database in the file private/smbpasswd has to be @@ -243,15 +236,5 @@ password. </sect2> -<sect2> -<title>Can I do this all with LDAP?</title> -<para>The simple answer is YES. Samba's pdb_ldap code supports -binding to a replica LDAP server, and will also follow referrals and -rebind to the master if it ever needs to make a modification to the -database. (Normally BDCs are read only, so this will not occur -often). -</para> -</sect2> - </sect1> </chapter> diff --git a/docs/docbook/projdoc/passdb.sgml b/docs/docbook/projdoc/Samba-LDAP-HOWTO.sgml index 222b4010ab..f294ddd1ff 100644 --- a/docs/docbook/projdoc/passdb.sgml +++ b/docs/docbook/projdoc/Samba-LDAP-HOWTO.sgml @@ -1,244 +1,27 @@ -<chapter id="passdb"> +<chapter id="samba-ldap-howto"> + <chapterinfo> <author> - <firstname>Jelmer</firstname><surname>Vernooij</surname> - <affiliation> - <orgname>The Samba Team</orgname> - <address><email>jelmer@samba.org</email></address> - </affiliation> - </author> - <author> <firstname>Gerald (Jerry)</firstname><surname>Carter</surname> <affiliation> <orgname>Samba Team</orgname> <address><email>jerry@samba.org</email></address> </affiliation> - </author> - <author> <firstname>Olivier (lem)</firstname><surname>Lemaire</surname> <affiliation> <orgname>IDEALX</orgname> <address><email>olem@IDEALX.org</email></address> </affiliation> </author> - <author> - <firstname>Jeremy</firstname><surname>Allison</surname> - <affiliation> - <orgname>Samba Team</orgname> - <address> - <email>jra@samba.org</email> - </address> - </affiliation> - </author> - <pubdate>February 2003</pubdate> -</chapterinfo> - -<title>User information database</title> - -<sect1> - <title>Introduction</title> - - <para>Old windows clients send plain text passwords over the wire. - Samba can check these passwords by crypting them and comparing them - to the hash stored in the unix user database. - </para> - - <para> - Newer windows clients send encrypted passwords (so-called - Lanman and NT hashes) over - the wire, instead of plain text passwords. The newest clients - will only send encrypted passwords and refuse to send plain text - passwords, unless their registry is tweaked. - </para> - - <para>These passwords can't be converted to unix style encrypted - passwords. Because of that you can't use the standard unix - user database, and you have to store the Lanman and NT hashes - somewhere else. </para> - - <para>Next to a differently encrypted passwords, - windows also stores certain data for each user - that is not stored in a unix user database, e.g. - workstations the user may logon from, the location where his/her - profile is stored, etc. - Samba retrieves and stores this information using a "passdb backend". - Commonly - available backends are LDAP, plain text file, MySQL and nisplus. - For more information, see the documentation about the - <command>passdb backend = </command> parameter. - </para> -</sect1> - -<sect1> - <title>Important Notes About Security</title> - - <para>The unix and SMB password encryption techniques seem similar - on the surface. This similarity is, however, only skin deep. The unix - scheme typically sends clear text passwords over the network when - logging in. This is bad. The SMB encryption scheme never sends the - cleartext password over the network but it does store the 16 byte - hashed values on disk. This is also bad. Why? Because the 16 byte hashed - values are a "password equivalent". You cannot derive the user's - password from them, but they could potentially be used in a modified - client to gain access to a server. This would require considerable - technical knowledge on behalf of the attacker but is perfectly possible. - You should thus treat the data stored in whatever - passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the - cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.</para> - - <para>Ideally we would like a password scheme which neither requires - plain text passwords on the net or on disk. Unfortunately this - is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc). </para> - - <warning> - <para>Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are <emphasis>never</emphasis> sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.</para> - - <para>Other Microsoft operating systems which also exhibit - this behavior includes</para> - - <simplelist> - <member>MS DOS Network client 3.0 with - the basic network redirector installed</member> - - <member>Windows 95 with the network redirector - update installed</member> - - <member>Windows 98 [se]</member> - - <member>Windows 2000</member> - </simplelist> - - <para><emphasis>Note :</emphasis>All current release of - Microsoft SMB/CIFS clients support authentication via the - SMB Challenge/Response mechanism described here. Enabling - clear text authentication does not disable the ability - of the client to participate in encrypted authentication.</para> - </warning> - - <sect2> - <title>Advantages of SMB Encryption</title> - - <simplelist> - <member>plain text passwords are not passed across - the network. Someone using a network sniffer cannot just - record passwords going to the SMB server.</member> - - <member>WinNT doesn't like talking to a server - that isn't using SMB encrypted passwords. It will refuse - to browse the server if the server is also in user level - security mode. It will insist on prompting the user for the - password on each connection, which is very annoying. The - only things you can do to stop this is to use SMB encryption. - </member> - </simplelist> - </sect2> - - - <sect2> - <title>Advantages of non-encrypted passwords</title> - - <simplelist> - <member>plain text passwords are not kept - on disk. </member> - - <member>uses same password file as other unix - services such as login and ftp</member> - - <member>you are probably already using other - services (such as telnet and ftp) which send plain text - passwords over the net, so sending them for SMB isn't - such a big deal.</member> - </simplelist> - </sect2> -</sect1> -<sect1> - <title>The smbpasswd Command</title> - - <para>The smbpasswd utility is a utility similar to the - <command>passwd</command> or <command>yppasswd</command> programs. - It maintains the two 32 byte password fields - in the passdb backend. </para> - - <para><command>smbpasswd</command> works in a client-server mode - where it contacts the local smbd to change the user's password on its - behalf. This has enormous benefits - as follows.</para> - - <para><command>smbpasswd</command> has the capability - to change passwords on Windows NT servers (this only works when - the request is sent to the NT Primary Domain Controller if you - are changing an NT Domain user's password).</para> - - <para>To run smbpasswd as a normal user just type :</para> - - <para><prompt>$ </prompt><userinput>smbpasswd</userinput></para> - <para><prompt>Old SMB password: </prompt><userinput><type old value here - - or hit return if there was no old password></userinput></para> - <para><prompt>New SMB Password: </prompt><userinput><type new value> - </userinput></para> - <para><prompt>Repeat New SMB Password: </prompt><userinput><re-type new value - </userinput></para> - - <para>If the old value does not match the current value stored for - that user, or the two new values do not match each other, then the - password will not be changed.</para> - - <para>If invoked by an ordinary user it will only allow the user - to change his or her own Samba password.</para> - - <para>If run by the root user smbpasswd may take an optional - argument, specifying the user name whose SMB password you wish to - change. Note that when run as root smbpasswd does not prompt for - or check the old password value, thus allowing root to set passwords - for users who have forgotten their passwords.</para> - - <para><command>smbpasswd</command> is designed to work in the same way - and be familiar to UNIX users who use the <command>passwd</command> or - <command>yppasswd</command> commands.</para> - - <para>For more details on using <command>smbpasswd</command> refer - to the man page which will always be the definitive reference.</para> -</sect1> - -<!-- -<sect1> -<title>The <command>pdbedit</command> command</title> -FIXME -</sect1> ---> - -<sect1> -<title>Plain text</title> -<para> -Older versions of samba retrieved user information from the unix user database -and eventually some other fields from the file <filename>/etc/samba/smbpasswd</filename> -or <filename>/etc/smbpasswd</filename>. When password encryption is disabled, no -data is stored at all. -</para> -</sect1> + <pubdate> (13 Jan 2002) </pubdate> +</chapterinfo> -<sect1> -<title>TDB</title> -<para>Samba can also store the user data in a "TDB" (Trivial Database). Using this backend -doesn't require any additional configuration. This backend is recommended for new installations who -don't require LDAP. -</para> -</sect1> +<title>Storing Samba's User/Machine Account information in an LDAP Directory</title> <sect1> -<title>LDAP</title> - -<sect2> -<title>Introduction</title> +<title>Purpose</title> <para> This document describes how to use an LDAP directory for storing Samba user @@ -272,9 +55,10 @@ Two additional Samba resources which may prove to be helpful are </para></listitem> </itemizedlist> -</sect2> +</sect1> -<sect2> + +<sect1> <title>Introduction</title> <para> @@ -346,9 +130,9 @@ versions of these libraries can be obtained from PADL Software the details of configuring these packages are beyond the scope of this document. </para> -</sect2> +</sect1> -<sect2> +<sect1> <title>Supported LDAP Servers</title> <para> @@ -361,15 +145,20 @@ hard to fix. If you are so inclined, please be sure to forward all patches to <ulink url="jerry@samba.org">jerry@samba.org</ulink>. </para> -</sect2> +</sect1> -<sect2> + + + +<sect1> <title>Schema and Relationship to the RFC 2307 posixAccount</title> <para> -Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in -<filename>examples/LDAP/samba.schema</filename>. The sambaAccount objectclass is given here: +Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in +<filename>examples/LDAP/samba.schema</filename>. (Note that this schema +file has been modified since the experimental support initially included +in 2.2.2). The sambaAccount objectclass is given here: </para> <para><programlisting> @@ -412,13 +201,13 @@ and functioning correctly. This division of information makes it possible to store all Samba account information in LDAP, but still maintain UNIX account information in NIS while the network is transitioning to a full LDAP infrastructure. </para> -</sect2> +</sect1> -<sect2> +<sect1> <title>Configuring Samba with LDAP</title> -<sect3> +<sect2> <title>OpenLDAP configuration</title> <para> @@ -477,10 +266,10 @@ index rid eq ##index cn eq ##index memberUid eq </programlisting></para> -</sect3> +</sect2> -<sect3> +<sect2> <title>Configuring Samba</title> <!--lem: <title>smb.conf LDAP parameters</title> --> @@ -541,11 +330,11 @@ use with an LDAP directory could appear as </programlisting></para> -</sect3> </sect2> +</sect1> -<sect2> +<sect1> <title>Accounts and Groups management</title> <para> @@ -564,15 +353,15 @@ file). </para> <para> -In Samba release 3.0, the group management system is based on posix -groups. This means that Samba make usage of the posixGroup objectclass. +In Samba release 2.2.3, the group management system is based on posix +groups. This meand that Samba make usage of the posixGroup objectclass. For now, there is no NT-like group system management (global and local groups). </para> -</sect2> +</sect1> -<sect2> +<sect1> <title>Security and sambaAccount</title> @@ -625,11 +414,11 @@ access to attrs=lmPassword,ntPassword </programlisting></para> -</sect2> +</sect1> -<sect2> +<sect1> <title>LDAP specials attributes for sambaAccounts</title> <para> @@ -722,11 +511,11 @@ something other than the default (e.g. \\MOBY\becky). </para> -</sect2> +</sect1> -<sect2> +<sect1> <title>Example LDIF Entries for a sambaAccount</title> @@ -781,189 +570,24 @@ pwdMustChange: 2147483647 ntPassword: 878D8014606CDA29677A44EFA1353FC7 </programlisting></para> -</sect2> -</sect1> -<sect1> -<title>MySQL</title> - -<sect2> -<title>Building</title> - -<para>To build the plugin, run <command>make bin/pdb_mysql.so</command> -in the <filename>source/</filename> directory of samba distribution. -</para> - -<para>Next, copy pdb_mysql.so to any location you want. I -strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</para> - -</sect2> - -<sect2> -<title>Creating the database</title> - -<para> -You either can set up your own table and specify the field names to pdb_mysql (see below -for the column names) or use the default table. The file <filename>examples/pdb/mysql/mysql.dump</filename> -contains the correct queries to create the required tables. Use the command : - -<command>mysql -u<replaceable>username</replaceable> -h<replaceable>hostname</replaceable> -p<replaceable>password</replaceable> <replaceable>databasename</replaceable> < <filename>/path/to/samba/examples/pdb/mysql/mysql.dump</filename></command> - -</para> -</sect2> - -<sect2> -<title>Configuring</title> - -<para>This plugin lacks some good documentation, but here is some short info:</para> - -<para>Add a the following to the <command>passdb backend</command> variable in your <filename>smb.conf</filename>: -<programlisting> -passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins] -</programlisting> -</para> - -<para>The identifier can be any string you like, as long as it doesn't collide with -the identifiers of other plugins or other instances of pdb_mysql. If you -specify multiple pdb_mysql.so entries in 'passdb backend', you also need to -use different identifiers! -</para> - -<para> -Additional options can be given thru the smb.conf file in the [global] section. -</para> - -<para><programlisting> -identifier:mysql host - host name, defaults to 'localhost' -identifier:mysql password -identifier:mysql user - defaults to 'samba' -identifier:mysql database - defaults to 'samba' -identifier:mysql port - defaults to 3306 -identifier:table - Name of the table containing users -</programlisting></para> - -<warning> -<para> -Since the password for the mysql user is stored in the -smb.conf file, you should make the the smb.conf file -readable only to the user that runs samba. This is considered a security -bug and will be fixed soon. -</para> -</warning> - -<para>Names of the columns in this table(I've added column types those columns should have first):</para> - -<para><programlisting> -identifier:logon time column - int(9) -identifier:logoff time column - int(9) -identifier:kickoff time column - int(9) -identifier:pass last set time column - int(9) -identifier:pass can change time column - int(9) -identifier:pass must change time column - int(9) -identifier:username column - varchar(255) - unix username -identifier:domain column - varchar(255) - NT domain user is part of -identifier:nt username column - varchar(255) - NT username -identifier:fullname column - varchar(255) - Full name of user -identifier:home dir column - varchar(255) - Unix homedir path -identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:') -identifier:logon script column - varchar(255) - Batch file to run on client side when logging on -identifier:profile path column - varchar(255) - Path of profile -identifier:acct desc column - varchar(255) - Some ASCII NT user data -identifier:workstations column - varchar(255) - Workstations user can logon to (or NULL for all) -identifier:unknown string column - varchar(255) - unknown string -identifier:munged dial column - varchar(255) - ? -identifier:uid column - int(9) - Unix user ID (uid) -identifier:gid column - int(9) - Unix user group (gid) -identifier:user sid column - varchar(255) - NT user SID -identifier:group sid column - varchar(255) - NT group ID -identifier:lanman pass column - varchar(255) - encrypted lanman password -identifier:nt pass column - varchar(255) - encrypted nt passwd -identifier:plain pass column - varchar(255) - plaintext password -identifier:acct control column - int(9) - nt user data -identifier:unknown 3 column - int(9) - unknown -identifier:logon divs column - int(9) - ? -identifier:hours len column - int(9) - ? -identifier:unknown 5 column - int(9) - unknown -identifier:unknown 6 column - int(9) - unknown -</programlisting></para> - -<para> -Eventually, you can put a colon (:) after the name of each column, which -should specify the column to update when updating the table. You can also -specify nothing behind the colon - then the data from the field will not be -updated. -</para> - -</sect2> - -<sect2> -<title>Using plaintext passwords or encrypted password</title> +</sect1> -<para> -I strongly discourage the use of plaintext passwords, however, you can use them: -</para> -<para> -If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords. -</para> -<para> -If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default. -</para> +<sect1> +<title>Comments</title> -</sect2> - -<sect2> -<title>Getting non-column data from the table</title> <para> -It is possible to have not all data in the database and making some 'constant'. -</para> +Please mail all comments regarding this HOWTO to <ulink +url="mailto:jerry@samba.org">jerry@samba.org</ulink>. This documents was +last updated to reflect the Samba 2.2.3 release. -<para> -For example, you can set 'identifier:fullname column' to : -<command>CONCAT(First_name,' ',Sur_name)</command> </para> -<para> -Or, set 'identifier:workstations column' to : -<command>NULL</command></para> - -<para>See the MySQL documentation for more language constructs.</para> -</sect2> </sect1> -<sect1> -<title>Passdb XML plugin</title> - -<sect2> -<title>Building</title> - -<para>This module requires libxml2 to be installed.</para> - -<para>To build pdb_xml, run: <command>make bin/pdb_xml.so</command> in -the directory <filename>source/</filename>. </para> - -</sect2> - -<sect2> -<title>Usage</title> - -<para>The usage of pdb_xml is pretty straightforward. To export data, use: - -<command>pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</command> - -(where filename is the name of the file to put the data in) -</para> - -<para> -To import data, use: -<command>pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</command> - -Where filename is the name to read the data from and current-pdb to put it in. -</para> -</sect2> -</sect1> </chapter> diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml index c0be81d989..7cf3e5735c 100644 --- a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml @@ -19,7 +19,7 @@ </chapterinfo> <title> -Samba as a NT4 or Win2k Primary Domain Controller +How to Configure Samba as a NT4 Primary Domain Controller </title> @@ -142,7 +142,7 @@ Implementing a Samba PDC can basically be divided into 2 broad steps. </para> -<orderedlist numeration="arabic"> +<orderedlist numeration="Arabic"> <listitem><para> Configuring the Samba PDC </para></listitem> @@ -426,7 +426,7 @@ be created manually. <para><programlisting> [global] - # <...remainder of parameters...> + # <...remainder of parameters...> add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </programlisting></para> @@ -496,7 +496,7 @@ version of Windows. </para> <para> - A 'machine name' in (typically) <filename>/etc/passwd</filename> + A 'machine name' in (typically) <filename>/etc/passwd</> of the machine name with a '$' appended. FreeBSD (and other BSD systems?) won't create a user with a '$' in their name. </para> @@ -504,7 +504,7 @@ version of Windows. <para> The problem is only in the program used to make the entry, once made, it works perfectly. So create a user without the '$' and - use <command>vipw</command> to edit the entry, adding the '$'. Or create + use <command>vipw</> to edit the entry, adding the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID ! </para> @@ -673,8 +673,8 @@ Here are some additional details: Policy Editor can be installed on an NT Workstation/Server, it will not work with NT policies because the registry key that are set by the policy templates. However, the files from the NT Server will run happily enough on an NTws. - You need <filename>poledit.exe, common.adm</filename> and <filename>winnt.adm</filename>. It is convenient - to put the two *.adm files in <filename>c:\winnt\inf</filename> which is where + You need <filename>poledit.exe, common.adm</> and <filename>winnt.adm</>. It is convenient + to put the two *.adm files in <filename>c:\winnt\inf</> which is where the binary will look for them unless told otherwise. Note also that that directory is 'hidden'. </para> @@ -928,7 +928,7 @@ general SMB topics such as browsing.</para> <listitem><para>See how Scott Merrill simulates a BDC behavior at <ulink url="http://www.skippy.net/linux/smb-howto.html"> - http://www.skippy.net/linux/smb-howto.html</ulink>. </para></listitem> + http://www.skippy.net/linux/smb-howto.html</>. </para></listitem> <listitem><para>Although 2.0.7 has almost had its day as a PDC, David Bannon will keep the 2.0.7 PDC pages at <ulink url="http://bioserve.latrobe.edu.au/samba"> @@ -958,8 +958,8 @@ general SMB topics such as browsing.</para> <para> There are a number of Samba related mailing lists. Go to <ulink url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror - and then click on <command>Support</command> and then click on <command> - Samba related mailing lists</command>. + and then click on <command>Support</> and then click on <command> + Samba related mailing lists</>. </para> <para> @@ -1028,8 +1028,8 @@ general SMB topics such as browsing.</para> <para>To have your name removed from a samba mailing list, go to the same place you went to to get on it. Go to <ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>, - click on your nearest mirror and then click on <command>Support</command> and - then click on <command> Samba related mailing lists</command>. Or perhaps see + click on your nearest mirror and then click on <command>Support</> and + then click on <command> Samba related mailing lists</>. Or perhaps see <ulink url="http://lists.samba.org/mailman/roster/samba-ntdom">here</ulink> </para> @@ -1112,7 +1112,7 @@ worthwhile lookingat how a Windows 9x/ME client performs a logon: <listitem> <para> The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -1704,7 +1704,7 @@ contrast to w95, where it _does_ transfer / update profiles correctly]. <sect1> <title> -DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba +DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba </title> <warning> diff --git a/docs/docbook/projdoc/UNIX_INSTALL.sgml b/docs/docbook/projdoc/UNIX_INSTALL.sgml index 5d0d388c08..1ff735a656 100644 --- a/docs/docbook/projdoc/UNIX_INSTALL.sgml +++ b/docs/docbook/projdoc/UNIX_INSTALL.sgml @@ -3,30 +3,81 @@ <title>How to Install and Test SAMBA</title> <sect1> - <title>Obtaining and installing samba</title> - - <para>Binary packages of samba are included in almost any Linux or - Unix distribution. There are also some packages available at - <ulink url="http://samba.org/">the samba homepage</ulink> - </para> - - <para>If you need to compile samba from source, check the - appropriate appendix chapter.</para> + <title>Read the man pages</title> + + <para>The man pages distributed with SAMBA contain + lots of useful info that will help to get you started. + If you don't know how to read man pages then try + something like:</para> + + <para><prompt>$ </prompt><userinput>man smbd.8</userinput> + or + <prompt>$ </prompt><userinput>nroff -man smbd.8 | more + </userinput> on older unixes.</para> + + <para>Other sources of information are pointed to + by the Samba web site,<ulink url="http://www.samba.org/"> + http://www.samba.org</ulink></para> </sect1> <sect1> - <title>Configuring samba</title> + <title>Building the Binaries</title> + + <para>To do this, first run the program <command>./configure + </command> in the source directory. This should automatically + configure Samba for your operating system. If you have unusual + needs then you may wish to run</para> + + <para><prompt>root# </prompt><userinput>./configure --help + </userinput></para> + + <para>first to see what special options you can enable. + Then executing</para> + + <para><prompt>root# </prompt><userinput>make</userinput></para> + + <para>will create the binaries. Once it's successfully + compiled you can use </para> + + <para><prompt>root# </prompt><userinput>make install</userinput></para> + + <para>to install the binaries and manual pages. You can + separately install the binaries and/or man pages using</para> + + <para><prompt>root# </prompt><userinput>make installbin + </userinput></para> + + <para>and</para> + + <para><prompt>root# </prompt><userinput>make installman + </userinput></para> - <para>Samba's configuration is stored in the smb.conf file, - that usually resides in <filename>/etc/samba/smb.conf</filename> - or <filename>/usr/local/samba/lib/smb.conf</filename>. You can either - edit this file yourself or do it using one of the many graphical - tools that are available, such as the web-based interface swat, that - is included with samba.</para> + <para>Note that if you are upgrading for a previous version + of Samba you might like to know that the old versions of + the binaries will be renamed with a ".old" extension. You + can go back to the previous version with</para> + + <para><prompt>root# </prompt><userinput>make revert + </userinput></para> -<sect2> - <title>Editing the smb.conf file</title> + <para>if you find this version a disaster!</para> +</sect1> + +<sect1> + <title>The all important step</title> + <para>At this stage you must fetch yourself a + coffee or other drink you find stimulating. Getting the rest + of the install right can sometimes be tricky, so you will + probably need it.</para> + + <para>If you have installed samba before then you can skip + this step.</para> +</sect1> + +<sect1> + <title>Create the smb configuration file. </title> + <para>There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in @@ -59,8 +110,9 @@ <para>For more information about security settings for the [homes] share please refer to the document UNIX_SECURITY.txt.</para> +</sect1> -<sect3> +<sect1> <title>Test your config file with <command>testparm</command></title> @@ -75,27 +127,105 @@ <para>Always run testparm again when you change <filename>smb.conf</filename>!</para> -</sect3> -</sect2> +</sect1> + +<sect1> + <title>Starting the smbd and nmbd</title> + + <para>You must choose to start smbd and nmbd either + as daemons or from <command>inetd</command>. Don't try + to do both! Either you can put them in <filename> + inetd.conf</filename> and have them started on demand + by <command>inetd</command>, or you can start them as + daemons either from the command line or in <filename> + /etc/rc.local</filename>. See the man pages for details + on the command line options. Take particular care to read + the bit about what user you need to be in order to start + Samba. In many cases you must be root.</para> + + <para>The main advantage of starting <command>smbd</command> + and <command>nmbd</command> using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request.</para> <sect2> - <title>SWAT</title> - - <para> - SWAT is a web-based interface that helps you configure samba. - SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage - on compiling, installing and configuring swat from source. - </para> - - <para>To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace <replaceable>localhost</replaceable> with the name of the computer you are running samba on if you - are running samba on a different computer then your browser.</para> - - <para>Note that you can attach to SWAT from any IP connected - machine but connecting from a remote machine leaves your - connection open to password sniffing as passwords will be sent - in the clear over the wire. </para> + <title>Starting from inetd.conf</title> + + <para>NOTE; The following will be different if + you use NIS or NIS+ to distributed services maps.</para> + + <para>Look at your <filename>/etc/services</filename>. + What is defined at port 139/tcp. If nothing is defined + then add a line like this:</para> + + <para><userinput>netbios-ssn 139/tcp</userinput></para> + + <para>similarly for 137/udp you should have an entry like:</para> + + <para><userinput>netbios-ns 137/udp</userinput></para> + + <para>Next edit your <filename>/etc/inetd.conf</filename> + and add two lines something like this:</para> + + <para><programlisting> + netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd + netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd + </programlisting></para> + + <para>The exact syntax of <filename>/etc/inetd.conf</filename> + varies between unixes. Look at the other entries in inetd.conf + for a guide.</para> + + <para>NOTE: Some unixes already have entries like netbios_ns + (note the underscore) in <filename>/etc/services</filename>. + You must either edit <filename>/etc/services</filename> or + <filename>/etc/inetd.conf</filename> to make them consistent.</para> + + <para>NOTE: On many systems you may need to use the + "interfaces" option in smb.conf to specify the IP address + and netmask of your interfaces. Run <command>ifconfig</command> + as root if you don't know what the broadcast is for your + net. <command>nmbd</command> tries to determine it at run + time, but fails on some unixes. See the section on "testing nmbd" + for a method of finding if you need to do this.</para> + + <para>!!!WARNING!!! Many unixes only accept around 5 + parameters on the command line in <filename>inetd.conf</filename>. + This means you shouldn't use spaces between the options and + arguments, or you should use a script, and start the script + from <command>inetd</command>.</para> + + <para>Restart <command>inetd</command>, perhaps just send + it a HUP. If you have installed an earlier version of <command> + nmbd</command> then you may need to kill nmbd as well.</para> + </sect2> + + <sect2> + <title>Alternative: starting it as a daemon</title> + + <para>To start the server as a daemon you should create + a script something like this one, perhaps calling + it <filename>startsmb</filename>.</para> + + <para><programlisting> + #!/bin/sh + /usr/local/samba/bin/smbd -D + /usr/local/samba/bin/nmbd -D + </programlisting></para> + + <para>then make it executable with <command>chmod + +x startsmb</command></para> + + <para>You can then run <command>startsmb</command> by + hand or execute it from <filename>/etc/rc.local</filename> + </para> + + <para>To kill it send a kill signal to the processes + <command>nmbd</command> and <command>smbd</command>.</para> + + <para>NOTE: If you use the SVR4 style init system then + you may like to look at the <filename>examples/svr4-startup</filename> + script to make Samba fit into that system.</para> </sect2> </sect1> @@ -150,8 +280,6 @@ <para>Try printing. eg:</para> - - <para><prompt>C:\WINDOWS\> </prompt><userinput>net use lpt1: \\servername\spoolservice</userinput></para> @@ -164,29 +292,90 @@ <sect1> <title>What If Things Don't Work?</title> - <para>Then you might read the file HOWTO chapter Diagnosis and the + <para>If nothing works and you start to think "who wrote + this pile of trash" then I suggest you do step 2 again (and + again) till you calm down.</para> + + <para>Then you might read the file DIAGNOSIS.txt and the FAQ. If you are still stuck then try the mailing list or newsgroup (look in the README for details). Samba has been successfully installed at thousands of sites worldwide, so maybe someone else has hit your problem and has overcome it. You could also use the WWW site to scan back issues of the samba-digest.</para> - <para>When you fix the problem <emphasis>please</emphasis> send some - updates of the documentation (or source code) to one of - the documentation maintainers or the list. - </para> + <para>When you fix the problem PLEASE send me some updates to the + documentation (or source code) so that the next person will find it + easier. </para> <sect2> + <title>Diagnosing Problems</title> + + <para>If you have installation problems then go to the + <ulink url="Diagnosis.html">Diagnosis</ulink> chapter to try to find the + problem.</para> + </sect2> + + <sect2> <title>Scope IDs</title> <para>By default Samba uses a blank scope ID. This means all your windows boxes must also have a blank scope ID. If you really want to use a non-blank scope ID then you will need to use the 'netbios scope' smb.conf option. - All your PCs will need to have the same setting for + All your PCs will need to have the same setting for this to work. I do not recommend scope IDs.</para> </sect2> + + <sect2> + <title>Choosing the Protocol Level</title> + + <para>The SMB protocol has many dialects. Currently + Samba supports 5, called CORE, COREPLUS, LANMAN1, + LANMAN2 and NT1.</para> + + <para>You can choose what maximum protocol to support + in the <filename>smb.conf</filename> file. The default is + NT1 and that is the best for the vast majority of sites.</para> + + <para>In older versions of Samba you may have found it + necessary to use COREPLUS. The limitations that led to + this have mostly been fixed. It is now less likely that you + will want to use less than LANMAN1. The only remaining advantage + of COREPLUS is that for some obscure reason WfWg preserves + the case of passwords in this protocol, whereas under LANMAN1, + LANMAN2 or NT1 it uppercases all passwords before sending them, + forcing you to use the "password level=" option in some cases.</para> + + <para>The main advantage of LANMAN2 and NT1 is support for + long filenames with some clients (eg: smbclient, Windows NT + or Win95). </para> + + <para>See the smb.conf(5) manual page for more details.</para> + + <para>Note: To support print queue reporting you may find + that you have to use TCP/IP as the default protocol under + WfWg. For some reason if you leave Netbeui as the default + it may break the print queue reporting on some systems. + It is presumably a WfWg bug.</para> + </sect2> + + <sect2> + <title>Printing from UNIX to a Client PC</title> + + <para>To use a printer that is available via a smb-based + server from a unix host with LPR you will need to compile the + smbclient program. You then need to install the script + "smbprint". Read the instruction in smbprint for more details. + </para> + + <para>There is also a SYSV style script that does much + the same thing called smbprint.sysv. It contains instructions.</para> + + <para>See the CUPS manual for information about setting up + printing from a unix host with CUPS to a smb-based server. </para> + </sect2> + <sect2> <title>Locking</title> @@ -243,5 +432,14 @@ <!-- FIXME: Sync this with oplocks.sgml --> </sect2> + + <sect2> + <title>Mapping Usernames</title> + + <para>If you have different usernames on the PCs and + the unix server then take a look at the "username map" option. + See the smb.conf man page for details.</para> + </sect2> + </sect1> </chapter> diff --git a/docs/docbook/projdoc/msdfs_setup.sgml b/docs/docbook/projdoc/msdfs_setup.sgml index a86cd74235..6e1609460f 100644 --- a/docs/docbook/projdoc/msdfs_setup.sgml +++ b/docs/docbook/projdoc/msdfs_setup.sgml @@ -4,7 +4,7 @@ <author> <firstname>Shirish</firstname><surname>Kalele</surname> <affiliation> - <orgname>Samba Team & Veritas Software</orgname> + <orgname>Samba Team & Veritas Software</orgname> <address> <email>samba@samba.org</email> </address> diff --git a/docs/docbook/projdoc/pdb_mysql.sgml b/docs/docbook/projdoc/pdb_mysql.sgml new file mode 100644 index 0000000000..59a134a15f --- /dev/null +++ b/docs/docbook/projdoc/pdb_mysql.sgml @@ -0,0 +1,146 @@ +<chapter id="pdb-mysql"> +<chapterinfo> + <author> + <firstname>Jelmer</firstname><surname>Vernooij</surname> + <affiliation> + <orgname>The Samba Team</orgname> + <address><email>jelmer@samba.org</email></address> + </affiliation> + </author> + <pubdate>November 2002</pubdate> +</chapterinfo> + +<title>Passdb MySQL plugin</title> + +<sect1> +<title>Building</title> + +<para>To build the plugin, run <command>make bin/pdb_mysql.so</command> +in the <filename>source/</filename> directory of samba distribution. +</para> + +<para>Next, copy pdb_mysql.so to any location you want. I +strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</para> + +</sect1> + +<sect1> +<title>Configuring</title> + +<para>This plugin lacks some good documentation, but here is some short info:</para> + +<para>Add a the following to the <command>passdb backend</command> variable in your <filename>smb.conf</filename>: +<programlisting> +passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins] +</programlisting> +</para> + +<para>The identifier can be any string you like, as long as it doesn't collide with +the identifiers of other plugins or other instances of pdb_mysql. If you +specify multiple pdb_mysql.so entries in 'passdb backend', you also need to +use different identifiers! +</para> + +<para> +Additional options can be given thru the smb.conf file in the [global] section. +</para> + +<para><programlisting> +identifier:mysql host - host name, defaults to 'localhost' +identifier:mysql password +identifier:mysql user - defaults to 'samba' +identifier:mysql database - defaults to 'samba' +identifier:mysql port - defaults to 3306 +identifier:table - Name of the table containing users +</programlisting></para> + +<para> +<emphasis> +WARNING: since the password for the mysql user is stored in the +smb.conf file, you should make the the smb.conf file +readable only to the user that runs samba. This is considered a security +bug and will be fixed soon.</emphasis> +</para> + +<para>Names of the columns in this table(I've added column types those columns should have first):</para> + +<para><programlisting> +identifier:logon time column - int(9) +identifier:logoff time column - int(9) +identifier:kickoff time column - int(9) +identifier:pass last set time column - int(9) +identifier:pass can change time column - int(9) +identifier:pass must change time column - int(9) +identifier:username column - varchar(255) - unix username +identifier:domain column - varchar(255) - NT domain user is part of +identifier:nt username column - varchar(255) - NT username +identifier:fullname column - varchar(255) - Full name of user +identifier:home dir column - varchar(255) - Unix homedir path +identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:') +identifier:logon script column - varchar(255) - Batch file to run on client side when logging on +identifier:profile path column - varchar(255) - Path of profile +identifier:acct desc column - varchar(255) - Some ASCII NT user data +identifier:workstations column - varchar(255) - Workstations user can logon to (or NULL for all) +identifier:unknown string column - varchar(255) - unknown string +identifier:munged dial column - varchar(255) - ? +identifier:uid column - int(9) - Unix user ID (uid) +identifier:gid column - int(9) - Unix user group (gid) +identifier:user sid column - varchar(255) - NT user SID +identifier:group sid column - varchar(255) - NT group ID +identifier:lanman pass column - varchar(255) - encrypted lanman password +identifier:nt pass column - varchar(255) - encrypted nt passwd +identifier:plain pass column - varchar(255) - plaintext password +identifier:acct control column - int(9) - nt user data +identifier:unknown 3 column - int(9) - unknown +identifier:logon divs column - int(9) - ? +identifier:hours len column - int(9) - ? +identifier:unknown 5 column - int(9) - unknown +identifier:unknown 6 column - int(9) - unknown +</programlisting></para> + +<para> +Eventually, you can put a colon (:) after the name of each column, which +should specify the column to update when updating the table. You can also +specify nothing behind the colon - then the data from the field will not be +updated. +</para> + +</sect1> + +<sect1> +<title>Using plaintext passwords or encrypted password</title> + +<para> +I strongly discourage the use of plaintext passwords, however, you can use them: +</para> + +<para> +If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords. +</para> + +<para> +If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default. +</para> + +</sect1> + +<sect1> +<title>Getting non-column data from the table</title> + +<para> +It is possible to have not all data in the database and making some 'constant'. +</para> + +<para> +For example, you can set 'identifier:fullname column' to : +<command>CONCAT(First_name,' ',Sur_name)</command> +</para> + +<para> +Or, set 'identifier:workstations column' to : +<command>NULL</command></para> + +<para>See the MySQL documentation for more language constructs.</para> + +</sect1> +</chapter> diff --git a/docs/docbook/projdoc/pdb_xml.sgml b/docs/docbook/projdoc/pdb_xml.sgml new file mode 100644 index 0000000000..87afb7b401 --- /dev/null +++ b/docs/docbook/projdoc/pdb_xml.sgml @@ -0,0 +1,42 @@ +<chapter id="pdb-xml"> +<chapterinfo> + <author> + <firstname>Jelmer</firstname><surname>Vernooij</surname> + <affiliation> + <orgname>The Samba Team</orgname> + <address><email>jelmer@samba.org</email></address> + </affiliation> + </author> + <pubdate>November 2002</pubdate> +</chapterinfo> + +<title>Passdb XML plugin</title> + +<sect1> +<title>Building</title> + +<para>This module requires libxml2 to be installed.</para> + +<para>To build pdb_xml, run: <command>make bin/pdb_xml.so</command> in +the directory <filename>source/</filename>. </para> + +</sect1> + +<sect1> +<title>Usage</title> + +<para>The usage of pdb_xml is pretty straightforward. To export data, use: + +<command>pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</command> + +(where filename is the name of the file to put the data in) +</para> + +<para> +To import data, use: +<command>pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</command> + +Where filename is the name to read the data from and current-pdb to put it in. +</para> +</sect1> +</chapter> diff --git a/docs/docbook/projdoc/printer_driver2.sgml b/docs/docbook/projdoc/printer_driver2.sgml index 8d15e437b2..7bca8dc6f5 100644 --- a/docs/docbook/projdoc/printer_driver2.sgml +++ b/docs/docbook/projdoc/printer_driver2.sgml @@ -409,8 +409,8 @@ echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP -touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 -chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 +chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 mkdir /var/spool/lpd/$2 chmod 700 /var/spool/lpd/$2 @@ -757,7 +757,7 @@ be: /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print + /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print </programlisting></para> <para> diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index efb14d4b6c..8cf16478c8 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -1,5 +1,6 @@ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!ENTITY UNIX-INSTALL SYSTEM "UNIX_INSTALL.sgml"> +<!ENTITY ENCRYPTION SYSTEM "ENCRYPTION.sgml"> <!ENTITY MS-Dfs-Setup SYSTEM "msdfs_setup.sgml"> <!ENTITY PRINTER-DRIVER2 SYSTEM "printer_driver2.sgml"> <!ENTITY DOMAIN-MEMBER SYSTEM "DOMAIN_MEMBER.sgml"> @@ -7,8 +8,10 @@ <!ENTITY NT-Security SYSTEM "NT_Security.sgml"> <!ENTITY Samba-PDC-HOWTO SYSTEM "Samba-PDC-HOWTO.sgml"> <!ENTITY Samba-BDC-HOWTO SYSTEM "Samba-BDC-HOWTO.sgml"> +<!ENTITY CVS-Access SYSTEM "CVS-Access.sgml"> <!ENTITY IntegratingWithWindows SYSTEM "Integrating-with-Windows.sgml"> <!ENTITY Samba-PAM SYSTEM "PAM-Authentication-And-Samba.sgml"> +<!ENTITY Samba-LDAP SYSTEM "Samba-LDAP-HOWTO.sgml"> <!ENTITY Diagnosis SYSTEM "Diagnosis.sgml"> <!ENTITY BUGS SYSTEM "Bugs.sgml"> <!ENTITY SECURITY-LEVEL SYSTEM "security_level.sgml"> @@ -19,11 +22,9 @@ <!ENTITY Portability SYSTEM "Portability.sgml"> <!ENTITY Other-Clients SYSTEM "Other-Clients.sgml"> <!ENTITY ADS-HOWTO SYSTEM "ADS-HOWTO.sgml"> -<!ENTITY Passdb SYSTEM "passdb.sgml"> +<!ENTITY pdb-mysql SYSTEM "pdb_mysql.sgml"> +<!ENTITY pdb-xml SYSTEM "pdb_xml.sgml"> <!ENTITY VFS SYSTEM "VFS.sgml"> -<!ENTITY GroupProfiles SYSTEM "GroupProfiles.sgml"> -<!ENTITY SecuringSamba SYSTEM "securing-samba.sgml"> -<!ENTITY Compiling SYSTEM "Compiling.sgml"> ]> <book id="Samba-HOWTO-Collection"> @@ -77,8 +78,9 @@ and how to configure the parts of samba you will most likely need. PLEASE read this.</para> </partintro> &UNIX-INSTALL; +&BROWSING; &BROWSING-Quick; -&Passdb; +&ENCRYPTION; </part> <part id="type"> @@ -110,19 +112,19 @@ part each cover one specific feature.</para> &MS-Dfs-Setup; &PRINTER-DRIVER2; &WINBIND; -&BROWSING; +&pdb-mysql; +&pdb-xml; &VFS; +&Samba-LDAP; +&CVS-Access; &GROUP-MAPPING-HOWTO; &SPEED; -&GroupProfiles; -&SecuringSamba; </part> <part id="Appendixes"> <title>Appendixes</title> &Portability; &Other-Clients; -&Compiling; &BUGS; &Diagnosis; </part> diff --git a/docs/docbook/projdoc/upgrading-to-3.0.sgml b/docs/docbook/projdoc/upgrading-to-3.0.sgml index f227556151..5b6b8dd635 100644 --- a/docs/docbook/projdoc/upgrading-to-3.0.sgml +++ b/docs/docbook/projdoc/upgrading-to-3.0.sgml @@ -16,24 +16,4 @@ FIXME </sect1> -<sect1> -<title>Obsolete configuration options</title> - -<para> -In 3.0, the following configuration options have been removed. -</para> - -<simplelist> -<member>printer driver</member> -<member>printer driver file</member> -<member>printer driver location</member> -<member>use rhosts</member> -<member>postscript</member> -</simplelist> - -<para>The first three options have been replaced by new driver procedures. -Please read the printing documentation.</para> - -</sect1> - </chapter> diff --git a/docs/docbook/projdoc/winbind.sgml b/docs/docbook/projdoc/winbind.sgml index 06579617f5..d2bfb8ab67 100644 --- a/docs/docbook/projdoc/winbind.sgml +++ b/docs/docbook/projdoc/winbind.sgml @@ -2,7 +2,6 @@ <chapterinfo> - <authorgroup> <author> <firstname>Tim</firstname><surname>Potter</surname> <affiliation> @@ -11,7 +10,7 @@ </affiliation> </author> <author> - <firstname>Andrew</firstname><surname>Tridgell</surname> + <firstname>Andrew</firstname><surname>Trigdell</surname> <affiliation> <orgname>Samba Team</orgname> <address><email>tridge@linuxcare.com.au</email></address> @@ -36,7 +35,6 @@ <address><email>jelmer@nl.linux.org</email></address> </affiliation> </author> - </authorgroup> <pubdate>27 June 2002</pubdate> </chapterinfo> @@ -175,7 +173,7 @@ <sect2> <title>Microsoft Remote Procedure Calls</title> - <para>Over the last few years, efforts have been underway + <para>Over the last two years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -194,21 +192,6 @@ </sect2> <sect2> - <title>Microsoft Active Directory Services</title> - - <para> - Since late 2001, Samba has gained the ability to - interact with Microsoft Windows 2000 using its 'Native - Mode' protocols, rather than the NT4 RPC services. - Using LDAP and Kerberos, a domain member running - winbind can enumerate users and groups in exactly the - same way as a Win2k client would, and in so doing - provide a much more efficient and - effective winbind implementation. - </para> - </sect2> - - <sect2> <title>Name Service Switch</title> <para>The Name Service Switch, or NSS, is a feature that is @@ -481,7 +464,7 @@ whether or not you have previously built the Samba binaries. <prompt>root#</prompt> <command>autoconf</command> <prompt>root#</prompt> <command>make clean</command> <prompt>root#</prompt> <command>rm config.cache</command> -<prompt>root#</prompt> <command>./configure</command> +<prompt>root#</prompt> <command>./configure --with-winbind</command> <prompt>root#</prompt> <command>make</command> <prompt>root#</prompt> <command>make install</command> </programlisting></para> @@ -569,7 +552,7 @@ include the following entries in the [global] section: <para><programlisting> [global] - <...> + <...> # separate domain and username with '+', like DOMAIN+username <ulink url="winbindd.8.html#WINBINDSEPARATOR">winbind separator</ulink> = + # use uids from 10000 to 20000 for domain users @@ -599,7 +582,7 @@ a domain user who has administrative privileges in the domain. <para> -<prompt>root#</prompt> <command>/usr/local/samba/bin/net join -S PDC -U Administrator</command> +<prompt>root#</prompt> <command>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</command> </para> @@ -750,7 +733,7 @@ start() { daemon /usr/local/samba/bin/winbindd RETVAL3=$? echo - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ RETVAL=1 return $RETVAL } @@ -777,7 +760,7 @@ stop() { echo -n $"Shutting down $KIND services: " killproc winbindd RETVAL3=$? - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb echo "" return $RETVAL } @@ -808,7 +791,7 @@ killproc() { # kill the named process(es) pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server @@ -1059,7 +1042,7 @@ annoying double prompts for passwords. </para> <para> -Now restart your Samba and try connecting through your application that you +Now restart your Samba & try connecting through your application that you configured in the pam.conf. </para> @@ -1080,7 +1063,7 @@ configured in the pam.conf. <itemizedlist> <listitem><para>Winbind is currently only available for - the Linux, Solaris and IRIX operating systems, although ports to other operating + the Linux operating system, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -1096,8 +1079,7 @@ configured in the pam.conf. <listitem><para>Currently the winbind PAM module does not take into account possible workstation and logon time restrictions - that may be been set for Windows NT users, this is - instead up to the PDC to enforce.</para></listitem> + that may be been set for Windows NT users.</para></listitem> </itemizedlist> </sect1> |