diff options
| author | Gerald Carter <jerry@samba.org> | 2001-06-22 16:53:39 +0000 |
|---|---|---|
| committer | Gerald Carter <jerry@samba.org> | 2001-06-22 16:53:39 +0000 |
| commit | 6c2edc0ea50bef81ac2ec08bae549deb6742234d (patch) | |
| tree | 9e29b8bc6a845585ee0ca9711895e695fa971646 /docs/htmldocs | |
| parent | d57410e0f9c28aa857c0ada934b71dbb0afec81f (diff) | |
| download | samba-6c2edc0ea50bef81ac2ec08bae549deb6742234d.tar.gz samba-6c2edc0ea50bef81ac2ec08bae549deb6742234d.tar.xz samba-6c2edc0ea50bef81ac2ec08bae549deb6742234d.zip | |
large set of updates from Richard Hellier <rlh@lsil.com>.
Mostly tag fixes and typos. Many Thanks! :)
Diffstat (limited to 'docs/htmldocs')
30 files changed, 928 insertions, 566 deletions
diff --git a/docs/htmldocs/CVS-Access.html b/docs/htmldocs/CVS-Access.html index ea47cede040..ff02a18f290 100644 --- a/docs/htmldocs/CVS-Access.html +++ b/docs/htmldocs/CVS-Access.html @@ -32,10 +32,10 @@ NAME="AEN3" >Introduction</A ></H1 ><P ->Samba is developed in an open environnment. Developers use CVS +>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 anonymouns CVS using the instructions +be accessed via anonymous CVS using the instructions detailed in this chapter.</P ><P >This document is a modified version of the instructions found at @@ -91,7 +91,7 @@ NAME="AEN16" >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 uptodate via normal cvs commands. This is the +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.</P ><P diff --git a/docs/htmldocs/ENCRYPTION.html b/docs/htmldocs/ENCRYPTION.html index f7424be11a4..cff06c4822a 100644 --- a/docs/htmldocs/ENCRYPTION.html +++ b/docs/htmldocs/ENCRYPTION.html @@ -118,7 +118,7 @@ NAME="AEN18" ><P >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 nextwork when + 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 @@ -196,7 +196,7 @@ CLASS="EMPHASIS" 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 particpate in encrypted authentication.</P + of the client to participate in encrypted authentication.</P ></TD ></TR ></TABLE diff --git a/docs/htmldocs/Integrating-with-Windows.html b/docs/htmldocs/Integrating-with-Windows.html index e8b0ac83d1f..7062b128529 100644 --- a/docs/htmldocs/Integrating-with-Windows.html +++ b/docs/htmldocs/Integrating-with-Windows.html @@ -609,12 +609,7 @@ needed in the smb.conf file:</P ><PRE CLASS="PROGRAMLISTING" > wins support = No - wins server = <TT -CLASS="REPLACEABLE" -><I ->xxx.xxx.xxx.xxx</I -></TT -></PRE + wins server = xxx.xxx.xxx.xxx</PRE ></P ><P >where <TT @@ -631,7 +626,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN122" +NAME="AEN121" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></H1 @@ -698,7 +693,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN132" +NAME="AEN131" >MS Windows security options and how to configure Samba for seemless integration</A ></H1 @@ -771,7 +766,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN149" +NAME="AEN148" >Use MS Windows NT as an authentication server</A ></H2 ><P @@ -807,7 +802,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN157" +NAME="AEN156" >Make Samba a member of an MS Windows NT security domain</A ></H2 ><P @@ -856,7 +851,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN171" +NAME="AEN170" >Configure Samba as an authentication server</A ></H2 ><P @@ -883,7 +878,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN178" +NAME="AEN177" >Users</A ></H3 ><P @@ -916,7 +911,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN185" +NAME="AEN184" >MS Windows NT Machine Accounts</A ></H3 ><P @@ -937,7 +932,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN190" +NAME="AEN189" >Configuration of Samba as ...</A ></H1 ><P diff --git a/docs/htmldocs/NT_Security.html b/docs/htmldocs/NT_Security.html index 43ba0566249..e7bf9890a9d 100644 --- a/docs/htmldocs/NT_Security.html +++ b/docs/htmldocs/NT_Security.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->UNIX Permission Bits and WIndows NT Access Control Lists</TITLE +>UNIX Permission Bits and Windows NT Access Control Lists</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD @@ -20,7 +20,7 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="AEN1" ->UNIX Permission Bits and WIndows NT Access Control Lists</A +>UNIX Permission Bits and Windows NT Access Control Lists</A ></H1 ><HR></DIV ><DIV @@ -153,7 +153,7 @@ CLASS="REPLACEABLE" >(Long name)</I ></TT > - is the discriptive string identifying the user (normally found in the + is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database). Click on the <B CLASS="COMMAND" >Close @@ -182,7 +182,7 @@ CLASS="COMMAND" you to change the ownership of this file to yourself (clicking on it will display a dialog box complaining that the user you are currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privilaged + for this is that changing the ownership of a file is a privileged operation in UNIX, available only to the <I CLASS="EMPHASIS" >root</I @@ -192,7 +192,7 @@ CLASS="EMPHASIS" client this will not work with Samba at this time.</P ><P >There is an NT chown command that will work with Samba - and allow a user with Administrator privillage connected + and allow a user with Administrator privilege connected to a Samba 2.0.4 server as root to change the ownership of files on both a local NTFS filesystem or remote mounted NTFS or Samba drive. This is available as part of the <I @@ -242,7 +242,7 @@ CLASS="REPLACEABLE" >(Long name)</I ></TT > - is the discriptive string identifying the user (normally found in the + is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).</P ><P >If the parameter <TT @@ -274,7 +274,7 @@ NAME="AEN58" ></H2 ><P >The standard UNIX user/group/world triple and - the correspinding "read", "write", "execute" permissions + the corresponding "read", "write", "execute" permissions triples are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into @@ -400,7 +400,7 @@ CLASS="COMMAND" button will not return a list of users in Samba 2.0.4 (it will give an error message of <B CLASS="COMMAND" ->"The remote proceedure call failed +>"The remote procedure call failed and did not execute"</B >). This means that you can only manipulate the current user/group/world permissions listed in @@ -450,7 +450,7 @@ CLASS="COMMAND" CLASS="COMMAND" >"Take Ownership"</B -> permission (dsplayed as <B +> permission (displayed as <B CLASS="COMMAND" >"O" </B @@ -582,7 +582,7 @@ CLASS="PARAMETER" ></A > parameter to provide compatibility with Samba 2.0.4 where the permission change facility was introduced. - To allow a user to modify all the user/group/world permissions on a file, + To allow a user to modify all the user/group/world permissions on a file with no restrictions set this parameter to 000.</P ><P >The <TT diff --git a/docs/htmldocs/OS2-Client-HOWTO.html b/docs/htmldocs/OS2-Client-HOWTO.html index 84a424c017e..d7a3132d151 100644 --- a/docs/htmldocs/OS2-Client-HOWTO.html +++ b/docs/htmldocs/OS2-Client-HOWTO.html @@ -173,7 +173,7 @@ NAME="AEN33" driver from an OS/2 system.</P ><P >Install the NT driver first for that printer. Then, - add to your smb.conf a paramater, "os2 driver map = + add to your smb.conf a parameter, "os2 driver map = <TT CLASS="REPLACEABLE" ><I diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 086636006e0..4bd9e671978 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -630,7 +630,7 @@ HREF="#AEN1494" ><DT >8. <A HREF="#AEN1519" ->Unifed Logons between Windows NT and UNIX using Winbind</A +>Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL @@ -712,7 +712,7 @@ HREF="#AEN1623" ><DT >9. <A HREF="#AEN1626" ->UNIX Permission Bits and WIndows NT Access Control Lists</A +>UNIX Permission Bits and Windows NT Access Control Lists</A ></DT ><DD ><DL @@ -915,7 +915,7 @@ CLASS="USERINPUT" ></P ><P >first to see what special options you can enable. - Then exectuting</P + Then executing</P ><P ><TT CLASS="PROMPT" @@ -1042,7 +1042,7 @@ CLASS="PROGRAMLISTING" >which would allow connections by anyone with an account on the server, using either their login name or "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for defails)</P + workgroup that Samba is part of. See BROWSING.txt for details)</P ><P >Note that <B CLASS="COMMAND" @@ -1089,7 +1089,7 @@ CLASS="FILENAME" not it will give an error message.</P ><P >Make sure it runs OK and that the services look - resonable before proceeding. </P + reasonable before proceeding. </P ></DIV ><DIV CLASS="SECT1" @@ -1207,7 +1207,7 @@ CLASS="FILENAME" <TT CLASS="FILENAME" >/etc/inetd.conf</TT -> to make them consistant.</P +> to make them consistent.</P ><P >NOTE: On many systems you may need to use the "interfaces" option in smb.conf to specify the IP address @@ -1220,7 +1220,7 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > tries to determine it at run - time, but fails on somunixes. See the section on "testing nmbd" + time, but fails on some unixes. See the section on "testing nmbd" for a method of finding if you need to do this.</P ><P >!!!WARNING!!! Many unixes only accept around 5 @@ -1495,7 +1495,7 @@ NAME="AEN176" >1.10.1. Diagnosing Problems</A ></H2 ><P ->If you have instalation problems then go to +>If you have installation problems then go to <TT CLASS="FILENAME" >DIAGNOSIS.txt</TT @@ -1629,7 +1629,7 @@ NAME="AEN196" are set by an application when it opens a file to determine what types of access should be allowed simultaneously with its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatability modes called + or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS.</P ><P >You can disable share modes using "share modes = no". @@ -1662,7 +1662,7 @@ NAME="AEN209" ><P >If you have problems using filenames with accented characters in them (like the German, French or Scandinavian - character sets) then I recommmend you look at the "valid chars" + character sets) then I recommend you look at the "valid chars" option in smb.conf and also take a look at the validchars package in the examples directory.</P ></DIV @@ -2857,7 +2857,7 @@ NAME="AEN446" ><P >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 nextwork when + 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 @@ -2933,7 +2933,7 @@ ALIGN="LEFT" 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 particpate in encrypted authentication.</P + of the client to participate in encrypted authentication.</P ></TD ></TR ></TABLE @@ -4123,7 +4123,7 @@ Add Printer Wizard icon. The APW will be show only if</P ><P >The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - priviledges (i.e. root or <TT + privileges (i.e. root or <TT CLASS="PARAMETER" ><I >printer admin</I @@ -4405,7 +4405,7 @@ foreach (supported architecture for a given driver) the Imprints tool set was the name space issues between various supported client architectures. For example, Windows NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 callsits version of this driver "Apple + and Windows 95 calls its version of this driver "Apple LaserWriter II NTX"</P ><P >The problem is how to know what client drivers have @@ -4455,7 +4455,7 @@ it will remember the server as a LanMan printer server. Upgrading the Samba host to 2.2 makes support for MSRPC printing possible, but the NT client will still remember the previous setting.</P ><P ->In order to give an NT client printing "amesia" (only necessary if you +>In order to give an NT client printing "amnesia" (only necessary if you want to use the newer MSRPC printing functionality in Samba), delete the registry keys associated with the print server contained in <TT @@ -4973,9 +4973,9 @@ NAME="AEN989" >7.1. Prerequisite Reading</A ></H1 ><P ->Before you continue readingin this chapter, please make sure +>Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services -in smb.conf and how to enable and administrate password +in smb.conf and how to enable and administer password encryption in Samba. Theses two topics are covered in the <A HREF="smb.conf.5.html" @@ -4986,7 +4986,7 @@ CLASS="FILENAME" ></A > manpage and the <A -HREF="EMCRYPTION.html" +HREF="ENCRYPTION.html" TARGET="_top" >Encryption chapter</A > @@ -5011,7 +5011,7 @@ CLASS="NOTE" >Author's Note :</EM > This document is a combination of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. -Both documents are superceeded by this one.</P +Both documents are superseded by this one.</P ></BLOCKQUOTE ></DIV ><P @@ -5384,7 +5384,7 @@ to the Domain</A >A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure communication with the Domain Controller. This is a security feature -to prevent an unauthorized machine with the same netbios name from +to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group accounts. Hence a Windows 9x host is never a true member of a domain because it does not posses a machine trust account, and thus has no shared secret with the DC.</P @@ -5417,7 +5417,7 @@ CLASS="FILENAME" ><P > Manual creation before joining the client to the domain. In this case, the password is set to a known value -- the lower case of the - machine's netbios name. + machine's NetBIOS name. </P ></LI ><LI @@ -5504,7 +5504,7 @@ CLASS="REPLACEABLE" >machine_name</I ></TT > absolutely must be -the netbios name of the pc to be added to the domain. The "$" must append the netbios +the NetBIOS name of the pc to be added to the domain. The "$" must append the NetBIOS name of the pc or samba will not recognize this as a machine account</P ><P >Now that the UNIX account has been created, the next step is to create @@ -5534,7 +5534,7 @@ CLASS="REPLACEABLE" ><I >machine_name</I ></TT -> is the machine's netbios +> is the machine's NetBIOS name. </P ><DIV CLASS="WARNING" @@ -5560,7 +5560,7 @@ ALIGN="LEFT" the "Server Manager". From the time at which the account is created to the time which th client joins the domain and changes the password, your domain is vulnerable to an intruder joining your domain using a - a machine with the same netbios name. A PDC inherently trusts + a machine with the same NetBIOS name. A PDC inherently trusts members of the domain and will serve out a large degree of user information to such clients. You have been warned! </P @@ -5741,8 +5741,8 @@ CLASS="PARAMETER" have not been created correctly. Make sure that you have the entry correct for the machine account in smbpasswd file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd - utility, make sure that the account name is the machine netbios name - with a '$' appended to it ( ie. computer_name$ ). There must be an entry + utility, make sure that the account name is the machine NetBIOS name + with a '$' appended to it ( i.e. computer_name$ ). There must be an entry in both /etc/passwd and the smbpasswd file. Some people have reported that inconsistent subnet masks between the Samba server and the NT client have caused this problem. Make sure that these are consistent @@ -5767,7 +5767,7 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbpasswd -e %user%</B ->, this is normaly done, when you create an account. +>, this is normally done, when you create an account. </P ><P > In order to work around this problem in 2.2.0, configure the @@ -5885,7 +5885,7 @@ CLASS="FILENAME" CLASS="COMMAND" >servicepackname /x</B >, - ie thats <B + i.e. that's <B CLASS="COMMAND" >Nt4sp6ai.exe /x</B > for service pack 6a. The policy editor, @@ -5998,7 +5998,7 @@ general SMB topics such as browsing.</P </P ><P > One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specifiy what + You can use the -d option for both smbd and nmbd to specify what 'debug level' at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords). @@ -6054,7 +6054,7 @@ TARGET="_top" (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of netmon that ships with SMS allows for dumping packets between any two - computers (ie. placing the network interface in promiscuous mode). + computers (i.e. placing the network interface in promiscuous mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon @@ -6306,7 +6306,7 @@ TARGET="_top" ><LI ><P > Don't cross post. Work out which is the best list to post to - and see what happens, ie don't post to both samba-ntdom and samba-technical. + and see what happens, i.e. don't post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more than one list and get annoyed to see the same message two or more times. Often someone will see a message and thinking it would be better dealt @@ -6412,7 +6412,7 @@ profiles for MS Windows for workgroups and MS Windows 9X clients.</P logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but very stupid) to create a domain where the user -database is not shared between servers, ie they are effectively workgroup +database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely involved with domains.</P @@ -6492,7 +6492,7 @@ TYPE="1" ><LI ><P > The client then connects to the user's home share and searches for the - user's profile. As it turns out, you can specify the users home share as + user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.profile. If the profiles are found, they are implemented. </P @@ -6620,7 +6620,7 @@ CLASS="PROGRAMLISTING" ></LI ><LI ><P -> you will probabaly find that your clients automatically mount the +> you will probably find that your clients automatically mount the \\SERVER\NETLOGON share as drive z: while logging in. You can put some useful programs there to execute from the batch files. </P @@ -6670,7 +6670,7 @@ or not Samba must be the domain master browser for its workgroup when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons are two distinctly different functions), it is not a good idea to -so. You should remember that the DC must register the DOMAIN#1b netbios +so. You should remember that the DC must register the DOMAIN#1b NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. For this reason, it is very wise to configure the Samba DC as the DMB.</P @@ -6735,7 +6735,7 @@ Win9X and WinNT clients implement these features.</P ><P >Win9X clients send a NetUserGetInfo request to the server to get the user's profiles location. However, the response does not have room for a separate -profiles location field, only the users home share. This means that Win9X +profiles location field, only the user's home share. This means that Win9X profiles are restricted to being in the user's home directory.</P ><P >WinNT clients send a NetSAMLogon RPC request, which contains many fields, @@ -6992,7 +6992,7 @@ TYPE="1" ></LI ><LI ><P -> search for the user's .PWL password-cacheing file in the c:\windows +> search for the user's .PWL password-caching file in the c:\windows directory, and delete it. </P ></LI @@ -7086,11 +7086,11 @@ case, or whether there is some configuration issue, as yet unknown, that makes NT Workstation _think_ that the link is a slow one is a matter to be resolved].</P ><P ->[lkcl 20aug97 - after samba digest correspondance, one user found, and +>[lkcl 20aug97 - after samba digest correspondence, one user found, and another confirmed, that profiles cannot be loaded from a samba server unless "security = user" and "encrypt passwords = yes" (see the file ENCRYPTION.txt) or "security = server" and "password server = ip.address. -of.yourNTserver" are used. either of these options will allow the NT +of.yourNTserver" are used. Either of these options will allow the NT workstation to access the samba server using LAN manager encrypted passwords, without the user intervention normally required by NT workstation for clear-text passwords].</P @@ -7282,7 +7282,7 @@ plain Servers.</P ><P >The User database is called the SAM (Security Access Manager) database and is used for all user authentication as well as for authentication of inter- -process authentication (ie: to ensure that the service action a user has +process authentication (i.e. to ensure that the service action a user has requested is permitted within the limits of that user's privileges).</P ><P >The Samba team have produced a utility that can dump the Windows NT SAM into @@ -7293,7 +7293,7 @@ to Samba systems.</P ><P >Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers can participate in a Domain security system that is controlled by Windows NT -servers that have been correctly configured. At most every domain will have +servers that have been correctly configured. Almost every domain will have ONE Primary Domain Controller (PDC). It is desirable that each domain will have at least one Backup Domain Controller (BDC).</P ><P @@ -7307,7 +7307,7 @@ CLASS="CHAPTER" ><HR><H1 ><A NAME="AEN1519" ->Chapter 8. Unifed Logons between Windows NT and UNIX using Winbind</A +>Chapter 8. Unified Logons between Windows NT and UNIX using Winbind</A ></H1 ><DIV CLASS="SECT1" @@ -7324,7 +7324,7 @@ NAME="AEN1537" >winbind </EM >, a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation + solution to the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind @@ -7355,7 +7355,7 @@ NAME="AEN1541" can lead to synchronization problems between the UNIX and Windows systems and confusion for users.</P ><P ->We divide the unifed logon problem for UNIX machines into +>We divide the unified logon problem for UNIX machines into three smaller problems:</P ><P ></P @@ -7382,7 +7382,7 @@ NAME="AEN1541" information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system. The winbind system provides a simple - and elegant solution to all three components of the unifed logon + and elegant solution to all three components of the unified logon problem.</P ></DIV ><DIV @@ -7509,7 +7509,7 @@ NAME="AEN1574" >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information - to be resolved from dierent sources. For example, a standalone + to be resolved from different sources. For example, a standalone UNIX workstation may resolve system information from a series of flat files stored on the local lesystem. A networked workstation may first attempt to resolve system information from local files, @@ -7538,7 +7538,7 @@ CLASS="FILENAME" for a line which matches the service type being requested, for example the "passwd" service type is used when user or group names are looked up. This config line species which implementations - of that service should be tried andin what order. If the passwd + of that service should be tried and in what order. If the passwd config line is:</P ><P ><B @@ -7588,7 +7588,7 @@ NAME="AEN1590" >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different - authentication methods for dierent system applications without + authentication methods for different system applications without having to recompile these applications. PAM is also useful for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users @@ -7603,7 +7603,7 @@ NAME="AEN1590" this change take eect directly on the Primary Domain Controller. </P ><P ->PAM is congured by providing control files in the directory +>PAM is configured by providing control files in the directory <TT CLASS="FILENAME" >/etc/pam.d/</TT @@ -7635,11 +7635,11 @@ NAME="AEN1598" ></H2 ><P >When a user or group is created under Windows NT - is it allocated a numerical relative identier (RID). This is - slightly dierent to UNIX which has a range of numbers which are + is it allocated a numerical relative identifier (RID). This is + slightly different to UNIX which has a range of numbers which are used to identify users, and the same range in which to identify groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is congured it is given part of the UNIX + vice versa. When winbind is configured it is given part of the UNIX user id space and a part of the UNIX group id space in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is allocated the next UNIX id from @@ -7666,7 +7666,7 @@ NAME="AEN1602" by NT domain controllers. User or group information returned by a PDC is cached by winbind along with a sequence number also returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modied. If + Windows NT whenever any user or group information is modified. If a cached entry has expired, the sequence number is requested from the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information @@ -7700,7 +7700,7 @@ CLASS="FILENAME" CLASS="COMMAND" >winbindd(8)</B > man page which will provide you - with conguration information and give you sample conguration files. + with configuration information and give you sample configuration files. You may also wish to update the main Samba daemons smbd and nmbd) with a more recent development release, such as the recently announced Samba 2.2 alpha release.</P @@ -7775,7 +7775,7 @@ CLASS="CHAPTER" ><HR><H1 ><A NAME="AEN1626" ->Chapter 9. UNIX Permission Bits and WIndows NT Access Control Lists</A +>Chapter 9. UNIX Permission Bits and Windows NT Access Control Lists</A ></H1 ><DIV CLASS="SECT1" @@ -7901,7 +7901,7 @@ CLASS="REPLACEABLE" >(Long name)</I ></TT > - is the discriptive string identifying the user (normally found in the + is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database). Click on the <B CLASS="COMMAND" >Close @@ -7930,7 +7930,7 @@ CLASS="COMMAND" you to change the ownership of this file to yourself (clicking on it will display a dialog box complaining that the user you are currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privilaged + for this is that changing the ownership of a file is a privileged operation in UNIX, available only to the <EM >root</EM > @@ -7939,7 +7939,7 @@ CLASS="COMMAND" client this will not work with Samba at this time.</P ><P >There is an NT chown command that will work with Samba - and allow a user with Administrator privillage connected + and allow a user with Administrator privilege connected to a Samba 2.0.4 server as root to change the ownership of files on both a local NTFS filesystem or remote mounted NTFS or Samba drive. This is available as part of the <EM @@ -7988,7 +7988,7 @@ CLASS="REPLACEABLE" >(Long name)</I ></TT > - is the discriptive string identifying the user (normally found in the + is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).</P ><P >If the parameter <TT @@ -8020,7 +8020,7 @@ NAME="AEN1692" ></H2 ><P >The standard UNIX user/group/world triple and - the correspinding "read", "write", "execute" permissions + the corresponding "read", "write", "execute" permissions triples are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into @@ -8146,7 +8146,7 @@ CLASS="COMMAND" button will not return a list of users in Samba 2.0.4 (it will give an error message of <B CLASS="COMMAND" ->"The remote proceedure call failed +>"The remote procedure call failed and did not execute"</B >). This means that you can only manipulate the current user/group/world permissions listed in @@ -8196,7 +8196,7 @@ CLASS="COMMAND" CLASS="COMMAND" >"Take Ownership"</B -> permission (dsplayed as <B +> permission (displayed as <B CLASS="COMMAND" >"O" </B @@ -8327,7 +8327,7 @@ CLASS="PARAMETER" ></A > parameter to provide compatibility with Samba 2.0.4 where the permission change facility was introduced. - To allow a user to modify all the user/group/world permissions on a file, + To allow a user to modify all the user/group/world permissions on a file with no restrictions set this parameter to 000.</P ><P >The <TT @@ -8689,7 +8689,7 @@ NAME="AEN1850" driver from an OS/2 system.</P ><P >Install the NT driver first for that printer. Then, - add to your smb.conf a paramater, "os2 driver map = + add to your smb.conf a parameter, "os2 driver map = <TT CLASS="REPLACEABLE" ><I @@ -8737,10 +8737,10 @@ NAME="AEN1866" >11.1. Introduction</A ></H1 ><P ->Samba is developed in an open environnment. Developers use CVS +>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 anonymouns CVS using the instructions +be accessed via anonymous CVS using the instructions detailed in this chapter.</P ><P >This document is a modified version of the instructions found at @@ -8796,7 +8796,7 @@ NAME="AEN1879" >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 uptodate via normal cvs commands. This is the +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.</P ><P diff --git a/docs/htmldocs/Samba-PDC-HOWTO.html b/docs/htmldocs/Samba-PDC-HOWTO.html index 883de3a0abb..1c67649f4ca 100644 --- a/docs/htmldocs/Samba-PDC-HOWTO.html +++ b/docs/htmldocs/Samba-PDC-HOWTO.html @@ -32,9 +32,9 @@ NAME="AEN3" >Prerequisite Reading</A ></H1 ><P ->Before you continue readingin this chapter, please make sure +>Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services -in smb.conf and how to enable and administrate password +in smb.conf and how to enable and administer password encryption in Samba. Theses two topics are covered in the <A HREF="smb.conf.5.html" @@ -45,7 +45,7 @@ CLASS="FILENAME" ></A > manpage and the <A -HREF="EMCRYPTION.html" +HREF="ENCRYPTION.html" TARGET="_top" >Encryption chapter</A > @@ -71,7 +71,7 @@ CLASS="EMPHASIS" >Author's Note :</I > This document is a combination of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. -Both documents are superceeded by this one.</P +Both documents are superseded by this one.</P ></BLOCKQUOTE ></DIV ><P @@ -435,7 +435,7 @@ to the Domain</A >A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure communication with the Domain Controller. This is a security feature -to prevent an unauthorized machine with the same netbios name from +to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group accounts. Hence a Windows 9x host is never a true member of a domain because it does not posses a machine trust account, and thus has no shared secret with the DC.</P @@ -468,7 +468,7 @@ CLASS="FILENAME" ><P > Manual creation before joining the client to the domain. In this case, the password is set to a known value -- the lower case of the - machine's netbios name. + machine's NetBIOS name. </P ></LI ><LI @@ -546,7 +546,7 @@ CLASS="REPLACEABLE" >machine_name</I ></TT > absolutely must be -the netbios name of the pc to be added to the domain. The "$" must append the netbios +the NetBIOS name of the pc to be added to the domain. The "$" must append the NetBIOS name of the pc or samba will not recognize this as a machine account</P ><P >Now that the UNIX account has been created, the next step is to create @@ -576,7 +576,7 @@ CLASS="REPLACEABLE" ><I >machine_name</I ></TT -> is the machine's netbios +> is the machine's NetBIOS name. </P ><DIV CLASS="WARNING" @@ -602,7 +602,7 @@ ALIGN="LEFT" the "Server Manager". From the time at which the account is created to the time which th client joins the domain and changes the password, your domain is vulnerable to an intruder joining your domain using a - a machine with the same netbios name. A PDC inherently trusts + a machine with the same NetBIOS name. A PDC inherently trusts members of the domain and will serve out a large degree of user information to such clients. You have been warned! </P @@ -781,8 +781,8 @@ CLASS="PARAMETER" have not been created correctly. Make sure that you have the entry correct for the machine account in smbpasswd file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd - utility, make sure that the account name is the machine netbios name - with a '$' appended to it ( ie. computer_name$ ). There must be an entry + utility, make sure that the account name is the machine NetBIOS name + with a '$' appended to it ( i.e. computer_name$ ). There must be an entry in both /etc/passwd and the smbpasswd file. Some people have reported that inconsistent subnet masks between the Samba server and the NT client have caused this problem. Make sure that these are consistent @@ -808,7 +808,7 @@ CLASS="EMPHASIS" CLASS="COMMAND" >smbpasswd -e %user%</B ->, this is normaly done, when you create an account. +>, this is normally done, when you create an account. </P ><P > In order to work around this problem in 2.2.0, configure the @@ -920,7 +920,7 @@ CLASS="FILENAME" CLASS="COMMAND" >servicepackname /x</B >, - ie thats <B + i.e. that's <B CLASS="COMMAND" >Nt4sp6ai.exe /x</B > for service pack 6a. The policy editor, @@ -1036,7 +1036,7 @@ CLASS="EMPHASIS" </P ><P > One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specifiy what + You can use the -d option for both smbd and nmbd to specify what 'debug level' at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords). @@ -1092,7 +1092,7 @@ TARGET="_top" (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of netmon that ships with SMS allows for dumping packets between any two - computers (ie. placing the network interface in promiscuous mode). + computers (i.e. placing the network interface in promiscuous mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon @@ -1347,7 +1347,7 @@ TARGET="_top" ><LI ><P > Don't cross post. Work out which is the best list to post to - and see what happens, ie don't post to both samba-ntdom and samba-technical. + and see what happens, i.e. don't post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more than one list and get annoyed to see the same message two or more times. Often someone will see a message and thinking it would be better dealt @@ -1455,7 +1455,7 @@ profiles for MS Windows for workgroups and MS Windows 9X clients.</P logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but very stupid) to create a domain where the user -database is not shared between servers, ie they are effectively workgroup +database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely involved with domains.</P @@ -1535,7 +1535,7 @@ TYPE="1" ><LI ><P > The client then connects to the user's home share and searches for the - user's profile. As it turns out, you can specify the users home share as + user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.profile. If the profiles are found, they are implemented. </P @@ -1636,7 +1636,7 @@ CLASS="PROGRAMLISTING" ></LI ><LI ><P -> you will probabaly find that your clients automatically mount the +> you will probably find that your clients automatically mount the \\SERVER\NETLOGON share as drive z: while logging in. You can put some useful programs there to execute from the batch files. </P @@ -1686,7 +1686,7 @@ or not Samba must be the domain master browser for its workgroup when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons are two distinctly different functions), it is not a good idea to -so. You should remember that the DC must register the DOMAIN#1b netbios +so. You should remember that the DC must register the DOMAIN#1b NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. For this reason, it is very wise to configure the Samba DC as the DMB.</P @@ -1752,7 +1752,7 @@ Win9X and WinNT clients implement these features.</P ><P >Win9X clients send a NetUserGetInfo request to the server to get the user's profiles location. However, the response does not have room for a separate -profiles location field, only the users home share. This means that Win9X +profiles location field, only the user's home share. This means that Win9X profiles are restricted to being in the user's home directory.</P ><P >WinNT clients send a NetSAMLogon RPC request, which contains many fields, @@ -1983,7 +1983,7 @@ CLASS="EMPHASIS" ></LI ><LI ><P -> search for the user's .PWL password-cacheing file in the c:\windows +> search for the user's .PWL password-caching file in the c:\windows directory, and delete it. </P ></LI @@ -2077,11 +2077,11 @@ case, or whether there is some configuration issue, as yet unknown, that makes NT Workstation _think_ that the link is a slow one is a matter to be resolved].</P ><P ->[lkcl 20aug97 - after samba digest correspondance, one user found, and +>[lkcl 20aug97 - after samba digest correspondence, one user found, and another confirmed, that profiles cannot be loaded from a samba server unless "security = user" and "encrypt passwords = yes" (see the file ENCRYPTION.txt) or "security = server" and "password server = ip.address. -of.yourNTserver" are used. either of these options will allow the NT +of.yourNTserver" are used. Either of these options will allow the NT workstation to access the samba server using LAN manager encrypted passwords, without the user intervention normally required by NT workstation for clear-text passwords].</P @@ -2274,7 +2274,7 @@ plain Servers.</P ><P >The User database is called the SAM (Security Access Manager) database and is used for all user authentication as well as for authentication of inter- -process authentication (ie: to ensure that the service action a user has +process authentication (i.e. to ensure that the service action a user has requested is permitted within the limits of that user's privileges).</P ><P >The Samba team have produced a utility that can dump the Windows NT SAM into @@ -2285,7 +2285,7 @@ to Samba systems.</P ><P >Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers can participate in a Domain security system that is controlled by Windows NT -servers that have been correctly configured. At most every domain will have +servers that have been correctly configured. Almost every domain will have ONE Primary Domain Controller (PDC). It is desirable that each domain will have at least one Backup Domain Controller (BDC).</P ><P diff --git a/docs/htmldocs/UNIX_INSTALL.html b/docs/htmldocs/UNIX_INSTALL.html index 34f4ed9283a..32c4b7be593 100644 --- a/docs/htmldocs/UNIX_INSTALL.html +++ b/docs/htmldocs/UNIX_INSTALL.html @@ -84,7 +84,7 @@ CLASS="USERINPUT" ></P ><P >first to see what special options you can enable. - Then exectuting</P + Then executing</P ><P ><TT CLASS="PROMPT" @@ -202,7 +202,7 @@ CLASS="PROGRAMLISTING" >which would allow connections by anyone with an account on the server, using either their login name or "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for defails)</P + workgroup that Samba is part of. See BROWSING.txt for details)</P ><P >Note that <B CLASS="COMMAND" @@ -249,7 +249,7 @@ CLASS="FILENAME" not it will give an error message.</P ><P >Make sure it runs OK and that the services look - resonable before proceeding. </P + reasonable before proceeding. </P ></DIV ><DIV CLASS="SECT1" @@ -358,7 +358,7 @@ CLASS="FILENAME" <TT CLASS="FILENAME" >/etc/inetd.conf</TT -> to make them consistant.</P +> to make them consistent.</P ><P >NOTE: On many systems you may need to use the "interfaces" option in smb.conf to specify the IP address @@ -371,7 +371,7 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > tries to determine it at run - time, but fails on somunixes. See the section on "testing nmbd" + time, but fails on some unixes. See the section on "testing nmbd" for a method of finding if you need to do this.</P ><P >!!!WARNING!!! Many unixes only accept around 5 @@ -637,7 +637,7 @@ NAME="AEN162" >Diagnosing Problems</A ></H2 ><P ->If you have instalation problems then go to +>If you have installation problems then go to <TT CLASS="FILENAME" >DIAGNOSIS.txt</TT @@ -771,7 +771,7 @@ NAME="AEN182" are set by an application when it opens a file to determine what types of access should be allowed simultaneously with its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatability modes called + or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS.</P ><P >You can disable share modes using "share modes = no". @@ -804,7 +804,7 @@ NAME="AEN195" ><P >If you have problems using filenames with accented characters in them (like the German, French or Scandinavian - character sets) then I recommmend you look at the "valid chars" + character sets) then I recommend you look at the "valid chars" option in smb.conf and also take a look at the validchars package in the examples directory.</P ></DIV diff --git a/docs/htmldocs/make_unicodemap.1.html b/docs/htmldocs/make_unicodemap.1.html index a0b87406936..b8b768ce40d 100644 --- a/docs/htmldocs/make_unicodemap.1.html +++ b/docs/htmldocs/make_unicodemap.1.html @@ -58,7 +58,7 @@ TARGET="_top" CLASS="COMMAND" >make_unicodemap</B > compiles text unicode map - files into binary unicodef map files for use with the + files into binary unicode map files for use with the internationalization features of Samba 2.2. </P ></DIV diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 4b2c39dc4a4..29bd8180407 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -539,7 +539,7 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > will accept SIGHUP, which will cause - it to dump out it's namelists into the file <TT + it to dump out its namelists into the file <TT CLASS="FILENAME" >namelist.debug </TT @@ -555,7 +555,7 @@ CLASS="FILENAME" cause <B CLASS="COMMAND" >nmbd</B -> to dump out it's server database in +> to dump out its server database in the <TT CLASS="FILENAME" >log.nmb</TT diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 0cce3000744..c87d7d35db9 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -128,7 +128,7 @@ CLASS="CONSTANT" datagrams. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX - systems root privilage is needed to bind to this port, and + systems root privilege is needed to bind to this port, and in addition, if the <A HREF="nmbd.8.html" TARGET="_top" diff --git a/docs/htmldocs/printer_driver2.html b/docs/htmldocs/printer_driver2.html index c44d9c5bf81..5bb83939a05 100644 --- a/docs/htmldocs/printer_driver2.html +++ b/docs/htmldocs/printer_driver2.html @@ -514,7 +514,7 @@ Add Printer Wizard icon. The APW will be show only if</P ><P >The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - priviledges (i.e. root or <TT + privileges (i.e. root or <TT CLASS="PARAMETER" ><I >printer admin</I @@ -788,7 +788,7 @@ foreach (supported architecture for a given driver) the Imprints tool set was the name space issues between various supported client architectures. For example, Windows NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 callsits version of this driver "Apple + and Windows 95 calls its version of this driver "Apple LaserWriter II NTX"</P ><P >The problem is how to know what client drivers have @@ -838,7 +838,7 @@ it will remember the server as a LanMan printer server. Upgrading the Samba host to 2.2 makes support for MSRPC printing possible, but the NT client will still remember the previous setting.</P ><P ->In order to give an NT client printing "amesia" (only necessary if you +>In order to give an NT client printing "amnesia" (only necessary if you want to use the newer MSRPC printing functionality in Samba), delete the registry keys associated with the print server contained in <TT diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 9c19660a461..53a0ea98dd2 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -137,7 +137,10 @@ CLASS="PROGRAMLISTING" ><P >set the debuglevel. Debug level 0 is the lowest and 100 being the highest. This should be set to 100 if you are - planning on submitting a bug report to the Samba team (see BUGS.txt). + planning on submitting a bug report to the Samba team (see <TT +CLASS="FILENAME" +>BUGS.txt</TT +>). </P ></DD ><DT @@ -152,7 +155,10 @@ CLASS="PROGRAMLISTING" ><DD ><P >File name for log/debug files. The extension - '.client' will be appended. The log file is never removed + <TT +CLASS="CONSTANT" +>'.client'</TT +> will be appended. The log file is never removed by the client. </P ></DD @@ -199,7 +205,7 @@ CLASS="ENVAR" <TT CLASS="ENVAR" >LOGNAME</TT -> variable and if either exist, the +> variable and if either exists, the string is uppercased. If these environmental variables are not found, the username <TT CLASS="CONSTANT" @@ -247,7 +253,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN90" +NAME="AEN92" ></A ><H2 >COMMANDS</H2 @@ -641,7 +647,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN210" +NAME="AEN212" ></A ><H2 >BUGS</H2 @@ -663,7 +669,7 @@ CLASS="COMMAND" available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work. Microsoft's implementation of these services has been demonstrated (and reported) - to be... a bit flakey in places. </P + to be... a bit flaky in places. </P ><P >The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in @@ -682,7 +688,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN220" +NAME="AEN222" ></A ><H2 >VERSION</H2 @@ -693,7 +699,7 @@ NAME="AEN220" ><DIV CLASS="REFSECT1" ><A -NAME="AEN223" +NAME="AEN225" ></A ><H2 >AUTHOR</H2 @@ -704,7 +710,7 @@ NAME="AEN223" to the way the Linux kernel is developed.</P ><P >The original rpcclient man page was written by Matthew - Geddes, Luke Kenneth Casson, and rewriten by Gerald Carter. + Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter.</P ></DIV diff --git a/docs/htmldocs/samba-pdc-faq.html b/docs/htmldocs/samba-pdc-faq.html index 058a5d5f518..d9c204bf1b5 100644 --- a/docs/htmldocs/samba-pdc-faq.html +++ b/docs/htmldocs/samba-pdc-faq.html @@ -45,9 +45,9 @@ NAME="AEN12" ></H1 ><P > This is the FAQ for Samba 2.2 as an NTDomain controller. - This document is derived from the origional FAQ that was built and + This document is derived from the original FAQ that was built and maintained by Gerald Carter from the early days of Samba NTDomain development - up until recently. It is now being updated as significent changes are + up until recently. It is now being updated as significant changes are made to 2.2.0. </P ><P @@ -165,7 +165,7 @@ HREF="#AEN103" ><A HREF="#AEN110" >"The machine account for this computer either does not -exist or is not accessable."</A +exist or is not accessible."</A ></DT ><DT ><A @@ -256,7 +256,7 @@ HREF="#AEN180" ><DT ><A HREF="#AEN182" ->What are 'Policies' ?.</A +>What are 'Policies' ?</A ></DT ><DT ><A @@ -314,12 +314,12 @@ HREF="#AEN248" ><A HREF="#AEN250" >What editor can I use in DOS/Windows that won't -mess with my unix EOF</A +mess with my unix EOF ?</A ></DT ><DT ><A HREF="#AEN263" ->How do I get 'User Manager' and 'Server Manager'</A +>How do I get 'User Manager' and 'Server Manager' ?</A ></DT ><DT ><A @@ -334,7 +334,7 @@ HREF="#AEN282" ><DT ><A HREF="#AEN286" ->How do I get my samba server to become a member ( not PDC ) of an NT domain?</A +>How do I get my samba server to become a member ( not PDC ) of an NT domain ?</A ></DT ></DL ></DD @@ -358,13 +358,13 @@ HREF="#AEN292" ><A HREF="#AEN294" >What are some diagnostics tools I can use to debug the domain logon process and where can I - find them?</A + find them ?</A ></DT ><DT ><A HREF="#AEN309" >How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?</A +or a Windows 9x box ?</A ></DT ></DL ></DD @@ -419,13 +419,13 @@ CLASS="FILENAME" > dialog will let you reset the smbpasswd. That is you don't need to do it from the unix box. However, at the present, you do need to have root as an - administrator and use the root user name and password.</P + administrator and use the root username and password.</P ><P ><B CLASS="COMMAND" >Policies</B > do work on a W2K machine. MS says that recent - builds of W2K dont observe an NT policy but it appears it does in 'legacy' + builds of W2K don't observe an NT policy but it appears it does in 'legacy' mode.</P ></DIV ><DIV @@ -437,7 +437,7 @@ NAME="AEN27" >Introduction</A ></H1 ><P -> This FAQ was origionally compiled by Jerry Carter (gc) chiefly dealing +> This FAQ was originally compiled by Jerry Carter (gc) chiefly dealing with the 'old HEAD' version of Samba and its NTDomain facilities. It is being rewritten by David Bannon (drb) so that it addresses more accurately the Samba 2.2.x release. @@ -454,7 +454,7 @@ TARGET="_top" </P ><P >Hopefully, as we all become familiar with the Samba 2.2 as a - PDC this document will become much more usefull.</P + PDC this document will become much more useful.</P ></DIV ></DIV ><DIV @@ -532,7 +532,7 @@ NAME="AEN37" ></LI ></UL ><P -> These things are note expected to work in the forseeable future: +> These things are not expected to work in the foreseeable future: </P ><P ></P @@ -558,7 +558,7 @@ controlled domain?</A ></H2 ><P > The 2.2 release branch of Samba supports Windows 2000 domain - clients in legacy mode, ie as if the PDC is a NTServer, not a + clients in legacy mode, i.e. as if the PDC is a NTServer, not a W2K server. </P ></DIV @@ -572,7 +572,7 @@ NAME="AEN65" >CVS</A ></H1 ><P -> CVS is a programme (publically available) that the Samba developers +> CVS is a program (publicly available) that the Samba developers use to maintain the central source code. Non developers can get access to the source in a read only capacity. Many flavours of unix now arrive with cvs installed.</P @@ -606,7 +606,7 @@ CLASS="VARIABLELIST" ><P >Samba 3.0 ? This code boasts all the main development work in Samba. Due to its developmental - nature, its not really suitable for production work. + nature, it's not really suitable for production work. </P ></DD ><DT @@ -693,7 +693,7 @@ controlled Domain?</A HREF="samba-pdc-howto.html" TARGET="_top" >HOWTO</A -> accessable from the samba web +> accessible from the samba web site under 'Documentation'. Read it. </P ></DIV @@ -734,11 +734,11 @@ CLASS="SECT2" ><A NAME="AEN110" >"The machine account for this computer either does not -exist or is not accessable."</A +exist or is not accessible."</A ></H2 ><P > When I try to join the domain I get the message "The machine account - for this computer either does not exist or is not accessable". Whats + for this computer either does not exist or is not accessible". Whats wrong ? </P ><P @@ -802,7 +802,7 @@ CLASS="COMMAND" path to the <B CLASS="COMMAND" >smbpasswd</B -> programme, do this : +> program, do this : </P ><P > <B @@ -812,7 +812,7 @@ CLASS="COMMAND" </P ><P > The entry will be created with a well known password, so any machine that - says its doppy could join the domain as long as it gets in first. So + says it's doppy could join the domain as long as it gets in first. So don't create the accounts any earlier than you need them. </P ></DIV @@ -854,7 +854,7 @@ when creating a machine account.</A ><P > This happens if you try to create a machine account from the machine itself and use a user name that does not work (for whatever - reason) and then try another (possibly valid) user name. + reason) and then try another (possibly valid) username. Exit out of the network applet to close the initial connection and try again. </P @@ -891,7 +891,7 @@ NAME="AEN143" ><P >I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message, "The system - can not log you on (C000019B), Please try a gain or consult your + can not log you on (C000019B), Please try again or consult your system administrator" when attempting to logon. </P ><P @@ -1029,14 +1029,14 @@ HREF="#AEN278" > </P ><P -> Make sure that the "logon path" is writeable by the user and make sure +> Make sure that the "logon path" is writable by the user and make sure that the connection to the logon path location is by the current user. - Sometimes Windows client do not drop the connection immediately upon + Sometimes Windows clients do not drop the connection immediately upon logoff. </P ><P > Some people have reported that the logon path location should - also be browseable. I (GC) have yet to emperically verify this, + also be browseable. I (GC) have yet to empirically verify this, but you can try.</P ></DIV ></DIV @@ -1054,13 +1054,13 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN182" ->What are 'Policies' ?.</A +>What are 'Policies' ?</A ></H2 ><P > When a user logs onto the domain via a client machine, the PDC sends the client machine a list of things contained in the 'policy' (if it exists). This list may do things like suppress - a splach screen, format the dates the way you like them or perhaps + a splash screen, format the dates the way you like them or perhaps remove locally stored profiles. </P ><P @@ -1070,7 +1070,7 @@ CLASS="FILENAME" >ntconfig.pol</TT > and located in the [netlogon] share. The file is created with a policy editor and must be readable - by anyone and writeable by only root. See <A + by anyone and writable by only root. See <A HREF="#AEN203" > below</A > for how to get a suitable editor. @@ -1102,7 +1102,7 @@ CLASS="PROGRAMLISTING" ></P ><P > A policy file must be in the [netlogon] share and must be - readable by everyone and writeable by only root. The file + readable by everyone and writable by only root. The file must be created by an NTServer <A HREF="#AEN203" >Policy @@ -1170,7 +1170,7 @@ CLASS="EMPHASIS" >. Further, although the Windows 95 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. + work with NT policies because of the registry keys that are set by the policy templates. However, the files from the NT Server will run happily enough on an NTws. You need <TT CLASS="FILENAME" @@ -1192,7 +1192,7 @@ CLASS="FILENAME" <B CLASS="COMMAND" >servicepackname /x</B ->, ie thats <B +>, i.e. that's <B CLASS="COMMAND" >Nt4sp6ai.exe /x</B @@ -1201,7 +1201,7 @@ CLASS="COMMAND" >poledt.exe</B > and the associated template files (*.adm) should - be extracted as well. It is also possible to downloaded the policy template + be extracted as well. It is also possible to download the policy template files for Office97 and get a copy of the policy editor. Another possible location is with the Zero Administration Kit available for download from Microsoft. </P @@ -1261,7 +1261,7 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/shadow</TT >). - In lots of situations thats OK, for example : + In lots of situations that's OK, for example : </P ><P ></P @@ -1278,10 +1278,10 @@ CLASS="FILENAME" ></LI ></UL ><P -> But sometimes you really do need to maintain two seperate password +> But sometimes you really do need to maintain two separate password databases and there are good reasons to keep then in sync. Trying to explain to users that they need to change their passwords in two - seperate places or use two seperate passwords is not fun. + separate places or use two separate passwords is not fun. </P ><P > However do understand that setting up password sync is not without @@ -1358,11 +1358,11 @@ CLASS="SECT2" ><A NAME="AEN250" >What editor can I use in DOS/Windows that won't -mess with my unix EOF</A +mess with my unix EOF ?</A ></H2 ><P >There are a number of Windows or DOS based editors that will - understand, and leave intact, the unix eof (as opposed to a DOS CL/LF). + understand, and leave intact, the unix eof (as opposed to a DOS CR/LF). List members suggested : </P ><P @@ -1390,7 +1390,7 @@ TARGET="_top" HREF="http://www.lancs.ac.uk/people/cpaap/pfe/" TARGET="_top" > www.lancs.ac.uk/people/cpaap/pfe/</A -> but its no longer being developed...</P +> but it's no longer being developed...</P ></LI ></UL ></DIV @@ -1400,7 +1400,7 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN263" ->How do I get 'User Manager' and 'Server Manager'</A +>How do I get 'User Manager' and 'Server Manager' ?</A ></H2 ><P > Since I don't need to buy an NT Server CD now, how do I get @@ -1409,7 +1409,7 @@ NAME="AEN263" ><P > Microsoft distributes a version of these tools called nexus for installation on Windows 95 systems. The - tools set includes + tool set includes </P ><P ></P @@ -1482,7 +1482,7 @@ CLASS="SECT2" CLASS="SECT2" ><A NAME="AEN286" ->How do I get my samba server to become a member ( not PDC ) of an NT domain?</A +>How do I get my samba server to become a member ( not PDC ) of an NT domain ?</A ></H2 ><P > Please refer to the <A @@ -1517,11 +1517,11 @@ CLASS="SECT2" ><A NAME="AEN294" >What are some diagnostics tools I can use to debug the domain logon process and where can I - find them?</A + find them ?</A ></H2 ><P > One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specifiy what + You can use the -d option for both smbd and nmbd to specify what 'debug level' at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords). @@ -1532,19 +1532,19 @@ NAME="AEN294" CLASS="COMMAND" >gcc -g </B > flag. This will include debug - information in the binaries and allow you to attch gdb to the + information in the binaries and allow you to attach gdb to the running smbd / nmbd process. In order to attach gdb to an smbd process for an NT workstation, first get the workstation to make the - connection. Pressing ctrl-alt-delete and going down to the domain box + connection. Pressing Ctrl-Alt-Del and going down to the domain box is sufficient (at least, on the first time you join the domain) to generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation maintains an open connection, and therefore there will be an smbd process running (assuming that you haven't set a really short smbd - idle timeout) So, in between pressing ctrl alt delete, and actually + idle timeout) So, in between pressing Ctrl-Alt-Del, and actually typing in your password, you can gdb attach and continue. </P ><P -> Some usefull samba commands worth investigating: +> Some useful samba commands worth investigating: </P ><P ></P @@ -1563,7 +1563,7 @@ CLASS="COMMAND" <A HREF="http://www.tcpdump.org/" TARGET="_top" ->http://www.tcpdup.org/</A +>http://www.tcpdump.org/</A >. Ethereal, another good packet sniffer for UNIX and Win32 hosts, can be downloaded from <A @@ -1573,11 +1573,11 @@ TARGET="_top" >. </P ><P -> For tracing things on the Microsoft Windows NT, Network Monitor +> For tracing things on Microsoft Windows NT, Network Monitor (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of netmon that ships with SMS allows for dumping packets between any two - computers (ie. placing the network interface in promiscuous mode). + computers (i.e. placing the network interface in promiscuous mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon @@ -1591,7 +1591,7 @@ CLASS="SECT2" ><A NAME="AEN309" >How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?</A +or a Windows 9x box ?</A ></H2 ><P > Installing netmon on an NT workstation requires a couple @@ -1732,13 +1732,13 @@ CLASS="EMPHASIS" ></LI ><LI ><P -> Ignacio Coupeau has a very comprehesive look at LDAP with Samba at +> Ignacio Coupeau has a very comprehensive look at LDAP with Samba at <A HREF="http://www.unav.es/cti/ldap-smb-howto.html" TARGET="_top" > http://www.unav.es/cti/ldap-smb-howto.html</A > - Be a little carefull however, I suspect that it does not specificly + Be a little careful however, I suspect that it does not specifically address samba 2.2.x. The HEAD pre-2.1 may possibly be the best stream to look at.</P ></LI @@ -1754,7 +1754,7 @@ HREF="http://www.kneschke.de/projekte/samba_tng" TARGET="_top" > http://www.kneschke.de/projekte/samba_tng</A >, but again, a - lot of it does not apply to the main stream Samba.</P + lot of it does not apply to the mainstream Samba.</P ></LI ><LI ><P @@ -1839,7 +1839,7 @@ TARGET="_top" >http://www.samba-tng.org/</A > It has been requested that you don't post questions about Samba-TNG to the - main stream Samba lists.</P + mainstream Samba lists.</P ><P ></P ><P @@ -1872,18 +1872,18 @@ TARGET="_top" > Try and make your question clear and brief, lots of long, convoluted questions get deleted before they are completely read ! Don't post html encoded messages (if you can select colour or font - size its html).</P + size it's html).</P ></LI ><LI ><P -> If you run one of those niffy 'I'm on holidays' things when +> If you run one of those nifty 'I'm on holidays' things when you are away, make sure its configured to not answer mailing lists. </P ></LI ><LI ><P > Don't cross post. Work out which is the best list to post to - and see what happens, ie don't post to both samba-ntdom and samba-technical. + and see what happens, i.e. don't post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more than one list and get annoyed to see the same message two or more times. Often someone will see a message and thinking it would be better dealt @@ -1943,7 +1943,7 @@ TARGET="_top" ></P ><P > Please don't post messages to the list asking to be removed, you will just - be refered to the above address (unless that process failed in some way...) + be referred to the above address (unless that process failed in some way...) </P ></DIV ></DIV diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 75e25876894..8d1e1577c55 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -756,7 +756,7 @@ CLASS="VARIABLELIST" upper case, or if they are forced to be the "default" case. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names - are lowered. Default <EM + are lowercased. Default <EM >yes</EM >.</P ></DD @@ -808,7 +808,7 @@ CLASS="REPLACEABLE" ></LI ><LI ><P ->The client's netbios name and any previously +>The client's NetBIOS name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding user.</P @@ -4224,7 +4224,7 @@ NAME="ADDPRINTERCOMMAND" NT/2000 print server.</P ><P >For a Samba host this means that the printer must be - physically added to underlying printing system. The <TT + physically added to the underlying printing system. The <TT CLASS="PARAMETER" ><I >add @@ -4727,7 +4727,11 @@ CLASS="CONSTANT" >domain</TT >. If it is set to no, then attempts to connect to a resource from - a domain or workgroup other than the one which smbd is running + a domain or workgroup other than the one which <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> is running in will fail, even if that domain is trusted by the remote server doing the authentication.</P ><P @@ -4785,7 +4789,7 @@ CLASS="COMMAND" ><A NAME="ANNOUNCEVERSION" ></A ->annouce version (G)</DT +>announce version (G)</DT ><DD ><P >This specifies the major and minor version numbers @@ -4852,7 +4856,7 @@ NAME="BINDINTERFACESONLY" ><DD ><P >This global parameter allows the Samba admin - to limit what interfaces on a machine will serve smb requests. If + to limit what interfaces on a machine will serve SMB requests. If affects file service <A HREF="smbd.8.html" TARGET="_top" @@ -5082,7 +5086,7 @@ TARGET="_top" ><P >If this parameter is set to <TT CLASS="CONSTANT" ->False</TT +>false</TT >, then Samba 2.2 will behave as previous versions of Samba would and will fail the lock request immediately if the lock range @@ -5360,7 +5364,11 @@ NAME="CHARACTERSET" >character set (G)</DT ><DD ><P ->This allows a smbd to map incoming filenames +>This allows <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> to map incoming filenames from a DOS Code page (see the <A HREF="#CLIENTCODEPAGE" >client @@ -6135,7 +6143,11 @@ NAME="DEBUGPID" ><DD ><P >When using only one log file for more then one - forked smbd-process there may be hard to follow which process + forked <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +>-process there may be hard to follow which process outputs which message. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on.</P ><P @@ -6761,13 +6773,16 @@ CLASS="PARAMETER" ></TT ></A > - option). If this option is set to False (the default) then if a vetoed + option). If this option is set to <TT +CLASS="CONSTANT" +>false</TT +> (the default) then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail. This is usually what you want.</P ><P >If this option is set to <TT CLASS="CONSTANT" ->True</TT +>true</TT >, then Samba will attempt to recursively delete any files and directories within the vetoed directory. This can be useful for integration with file @@ -7078,7 +7093,10 @@ NAME="DIRECTORYSECURITYMASK" Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave - it as the default of 0777.</P + it as the default of <TT +CLASS="CONSTANT" +>0777</TT +>.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -7266,7 +7284,10 @@ NAME="DOMAINLOGONS" >domain logons (G)</DT ><DD ><P ->If set to true, the Samba server will serve +>If set to <TT +CLASS="CONSTANT" +>true</TT +>, the Samba server will serve Windows 95/98 Domain logons for the <A HREF="#WORKGROUP" > <TT @@ -7445,7 +7466,7 @@ NAME="DOSFILEMODE" ><DD ><P > The default behavior in Samba is to provide - UNIX-like behavor where only the owner of a file/directory is + UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it. However, this behavior is often confusing to DOS/Windows users. Enabling this parameter allows a user who has write access to the file (by whatever @@ -7514,8 +7535,12 @@ CLASS="COMMAND" > is acting on behalf of is not the file owner. Setting this option to <TT CLASS="CONSTANT" -> True</TT -> allows DOS semantics and smbd will change the file +> true</TT +> allows DOS semantics and <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> will change the file timestamp as DOS requires.</P ><P >Default: <B @@ -7567,7 +7592,7 @@ CLASS="COMMAND" > program for information on how to set up and maintain this file), or set the <A HREF="#SECURITY" ->security=[serve|domain]</A +>security=[server|domain]</A > parameter which causes <B CLASS="COMMAND" @@ -7588,18 +7613,18 @@ NAME="ENHANCEDBROWSING" ><DD ><P >This option enables a couple of enhancements to - cross-subnet browse propogation that have been added in Samba + cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations. <EM >These enhancements are currently only available in the HEAD Samba CVS tree (not Samba 2.2.x).</EM ></P ><P ->The first enhancement to browse propogation consists of a regular +>The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, - followed by a browse synchronisation with each of the returned + followed by a browse synchronization with each of the returned DMBs. The second enhancement consists of a regular randomised browse - synchronisation with all currently known DMBs.</P + synchronization with all currently known DMBs.</P ><P >You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists. Due to the restrictions @@ -7607,7 +7632,7 @@ NAME="ENHANCEDBROWSING" to stay around forever which can be annoying.</P ><P >In general you should leave this option enabled as it makes - cross-subnet browse propogation much more reliable.</P + cross-subnet browse propagation much more reliable.</P ><P >Default: <B CLASS="COMMAND" @@ -7704,7 +7729,7 @@ NAME="FAKEDIRECTORYCREATETIMES" reported by Samba will be updated whenever a file is created or or deleted in the directory. NMAKE finds all object files in the object directory. The timestamp of the last one built is then - compared to the timestamp of the object dircetory. If the + compared to the timestamp of the object directory. If the directory's timestamp if newer, then all object files will be rebuilt. Enabling this option ensures directories always predate their contents and an NMAKE build @@ -7843,7 +7868,10 @@ CLASS="PARAMETER" mask</I ></TT ></A -> to true.</P +> to <TT +CLASS="CONSTANT" +>true</TT +>.</P ><P >See also the parameter <A HREF="#CREATEMASK" @@ -7915,7 +7943,10 @@ CLASS="PARAMETER" mask</I ></TT ></A -> to true.</P +> to <TT +CLASS="CONSTANT" +>true</TT +>.</P ><P >See also the parameter <A HREF="#DIRECTORYMASK" @@ -8268,7 +8299,7 @@ CLASS="PARAMETER" </A >parameter is set to <TT CLASS="CONSTANT" ->False</TT +>false</TT >.</P ><P >Default: <B @@ -8538,7 +8569,7 @@ CLASS="PARAMETER" ></A > is <TT CLASS="CONSTANT" ->True</TT +>true</TT >, and <A HREF="smbd.8.html" TARGET="_top" @@ -8817,7 +8848,7 @@ CLASS="PARAMETER" > hosts equiv</I ></TT > may be useful for NT clients which will - not supply passwords to samba.</P + not supply passwords to Samba.</P ><P ><EM >NOTE :</EM @@ -8976,7 +9007,7 @@ CLASS="PARAMETER" inheritance (the code explicitly prohibits this).</P ><P >This can be particularly useful on large systems with - many users, perhaps several thousand,to allow a single [homes] + many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user.</P ><P >See also <A @@ -9286,8 +9317,12 @@ NAME="LANMANAUTH" >lanman auth (G)</DT ><DD ><P ->This parameter determines whether or not smbd will - attempt to authentication users using the LANMAN password hash. +>This parameter determines whether or not <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> 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.</P @@ -9350,7 +9385,10 @@ CLASS="PARAMETER" ></TT > </A -> parameter must be set to "true" on this share in order for +> parameter must be set to <TT +CLASS="CONSTANT" +>true</TT +> on this share in order for this parameter to have any effect.</P ><P >See also the <A @@ -9543,13 +9581,19 @@ CLASS="COMMAND" > to try and become a local master browser on a subnet. If set to <TT CLASS="CONSTANT" ->False</TT +>false</TT > then <B CLASS="COMMAND" > nmbd</B > will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By - default this value is set to true. Setting this value to true doesn't + default this value is set to <TT +CLASS="CONSTANT" +>true</TT +>. Setting this value to <TT +CLASS="CONSTANT" +>true</TT +> doesn't mean that Samba will <EM >become</EM > the local master @@ -9560,7 +9604,10 @@ CLASS="COMMAND" > participate</EM > in elections for local master browser.</P ><P ->Setting this value to False will cause <B +>Setting this value to <TT +CLASS="CONSTANT" +>false</TT +> will cause <B CLASS="COMMAND" >nmbd</B > @@ -9651,7 +9698,7 @@ CLASS="COMMAND" filesystems which <EM >may</EM > not need locking (such as - cdrom drives), although setting this parameter of <TT + CDROM drives), although setting this parameter of <TT CLASS="CONSTANT" >no</TT > @@ -9864,7 +9911,7 @@ CLASS="FILENAME" ><P >The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT - client. The share must be writeable when the logs in for the first + client. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories.</P ><P @@ -9908,7 +9955,7 @@ NAME="LOGONSCRIPT" >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 - style cr/lf line endings. Using a DOS-style editor to create the + style CR/LF line endings. Using a DOS-style editor to create the file is recommended.</P ><P >The script must be a relative path to the [netlogon] @@ -9935,7 +9982,7 @@ CLASS="FILENAME" >/usr/local/samba/netlogon/STARTUP.BAT</TT ></P ><P ->The contents of the batch file is entirely your choice. A +>The contents of the batch file are entirely your choice. A suggested command would be to add <B CLASS="COMMAND" >NET TIME \\SERVER /SET @@ -9992,7 +10039,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. A <TT CLASS="PARAMETER" ><I @@ -10173,7 +10220,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P ><P @@ -10243,7 +10290,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. A <TT CLASS="PARAMETER" ><I @@ -10329,7 +10376,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. A <TT CLASS="PARAMETER" ><I @@ -10387,7 +10434,7 @@ NAME="MACHINEPASSWORDTIMEOUT" >machine password timeout (G)</DT ><DD ><P ->If a Samba server is a member of an Windows +>If a Samba server is a member of a Windows NT Domain (see the <A HREF="#SECURITYEQUALSDOMAIN" >security=domain</A @@ -10476,8 +10523,8 @@ NAME="MAGICSCRIPT" executed on behalf of the connected user.</P ><P >Scripts executed in this way will be deleted upon - completion assuming that the user has the appripriate level - of priviledge and the ile permissions allow the deletion.</P + completion assuming that the user has the appropriate level + of privilege and the file permissions allow the deletion.</P ><P >If the script generates output, output will be sent to the file specified by the <A @@ -10539,7 +10586,7 @@ NAME="MANGLEDMAP" ><DD ><P >This is for those who want to directly map UNIX - file names which can not be represented on Windows/DOS. The mangling + file names which cannot be represented on Windows/DOS. The mangling of names is not always what is needed. In particular you may have documents with file extensions that differ between DOS and UNIX. For example, under UNIX it is common to use <TT @@ -10570,7 +10617,7 @@ CLASS="COMMAND" CLASS="FILENAME" >;1 </TT -> off the ends of filenames on some CDROMS (only visible +> off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).</P ><P >Default: <EM @@ -10687,12 +10734,12 @@ TARGET="_top" ><P >The larger this value, the more likely it is that mangled names can be successfully converted to correct long UNIX names. - However, large stack sizes will slow most directory access. Smaller + However, large stack sizes will slow most directory accesses. Smaller stacks save memory in the server (each stack element costs 256 bytes). </P ><P >It is not possible to absolutely guarantee correct long - file names, so be prepared for some surprises!</P + filenames, so be prepared for some surprises!</P ><P >Default: <B CLASS="COMMAND" @@ -11077,7 +11124,7 @@ NAME="MAXMUX" ><DD ><P >This option controls the maximum number of - outstanding simultaneous SMB operations that samba tells the client + outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.</P ><P >Default: <B @@ -11250,10 +11297,14 @@ CLASS="COMMAND" ></A > processes concurrently running on a system and is intended - as a stop gap to prevent degrading service to clients in the event + 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 smbd associated with him or her + conditions, each user will have an <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> associated with him or her to handle connections to all shares from a given host. </P ><P @@ -11391,7 +11442,7 @@ CLASS="COMMAND" >. That's why I have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover - after 30secs, hopefully).</P + after 30 seconds, hopefully).</P ><P >All messages are delivered as the global guest user. The command takes the standard substitutions, although <TT @@ -12188,7 +12239,11 @@ TARGET="_top" improve the efficiency of the granting of oplocks under multiple client contention for the same file.</P ><P ->In brief it specifies a number, which causes smbd not to +>In brief it specifies a number, which causes <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> 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 <B @@ -12214,7 +12269,10 @@ NAME="OPLOCKS" >oplocks (S)</DT ><DD ><P ->This boolean option tells smbd whether to +>This boolean option tells <B +CLASS="COMMAND" +>smbd</B +> whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve the speed of access to files on Samba servers. It allows the clients @@ -12336,7 +12394,7 @@ NAME="OS2DRIVERMAP" name>.<device name></P ><P >For example, a valid entry using the HP LaserJet 5 - printer driver woudl appear as <B + printer driver would appear as <B CLASS="COMMAND" >HP LaserJet 5L = LASERJET.HP LaserJet 5L</B @@ -12381,7 +12439,7 @@ CLASS="PARAMETER" ></TT ></A > must be - be changed to work with the pam prompts. + be changed to work with the PAM prompts. </P ><P >Default: <B @@ -12434,7 +12492,7 @@ HREF="smbd.8.html" TARGET="_top" >smbd</A > and the local password changing - program to change the users password. The string describes a + program to change the user's password. The string describes a sequence of response-receive pairs that <A HREF="smbd.8.html" TARGET="_top" @@ -12491,8 +12549,8 @@ CLASS="CONSTANT" in them into a single string.</P ><P >If the send string in any part of the chat sequence - is a fullstop ".", then no string is sent. Similarly, - if the expect string is a fullstop then no string is expected.</P + is a full stop ".", then no string is sent. Similarly, + if the expect string is a full stop then no string is expected.</P ><P >Note that if the <A HREF="#UNIXPASSWORDSYNC" @@ -12503,7 +12561,10 @@ CLASS="PARAMETER" password sync</I ></TT ></A -> parameter is set to true, then this +> parameter is set to <TT +CLASS="CONSTANT" +>true</TT +>, then this sequence is called <EM >AS ROOT</EM > when the SMB password @@ -12520,12 +12581,15 @@ CLASS="PARAMETER" password change</I ></TT ></A -> parameter is set to true, then the +> parameter is set to <TT +CLASS="CONSTANT" +>true</TT +>, then the chat sequence should consist of three elements. The first element should - match the pam prompt for the old password, the second element should match - the pam prompt for the first request for the new password, and the final - element should match the pam prompt for the second request for the new password. - These matches are done case insentively. Under most conditions this change + match the PAM prompt for the old password, the second element should match + the PAM prompt for the first request for the new password, and the final + element should match the PAM prompt for the second request for the new password. + These matches are done case insensitively. Under most conditions this change is done as root so the prompt for the old password will never be matched. </P ><P @@ -12683,7 +12747,7 @@ CLASS="PARAMETER" ></TT > parameter is set to <TT CLASS="CONSTANT" ->True +>true </TT > then this program is called <EM >AS ROOT</EM @@ -12720,7 +12784,7 @@ CLASS="PARAMETER" ></TT > is set to <TT CLASS="CONSTANT" ->False</TT +>false</TT >.</P ><P >See also <A @@ -12967,7 +13031,7 @@ CLASS="COMMAND" CLASS="COMMAND" > security=server</B > mode the network logon will appear to - come from there rather than from the users workstation.</P + come from there rather than from the user's workstation.</P ></LI ></UL ><P @@ -13092,7 +13156,7 @@ NAME="POSTEXEC" substitutions. The command may be run as the root on some systems.</P ><P ->An interesting example may be do unmount server +>An interesting example may be to unmount server resources:</P ><P ><B @@ -13130,7 +13194,7 @@ NAME="POSTSCRIPT" ><DD ><P >This parameter forces a printer to interpret - the print files as postscript. This is done by adding a <TT + the print files as PostScript. This is done by adding a <TT CLASS="CONSTANT" >%! </TT @@ -13235,7 +13299,10 @@ TARGET="_top" > is a preferred master browser for its workgroup.</P ><P ->If this is set to true, on startup, <B +>If this is set to <TT +CLASS="CONSTANT" +>true</TT +>, on startup, <B CLASS="COMMAND" >nmbd</B > @@ -13706,7 +13773,7 @@ NAME="PRINTERDRIVER" ><P ><EM >Note :</EM ->This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in <TT @@ -13766,7 +13833,7 @@ NAME="PRINTERDRIVERFILE" ><P ><EM >Note :</EM ->This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in <TT @@ -13839,7 +13906,7 @@ NAME="PRINTERDRIVERLOCATION" ><P ><EM >Note :</EM ->This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in <TT @@ -13977,7 +14044,7 @@ CLASS="PARAMETER" >lprm command</I ></TT > if specified in the - [global]f> section.</P + [global] section.</P ><P >Currently eight printing styles are supported. They are <TT @@ -14070,14 +14137,14 @@ NAME="QUEUEPAUSECOMMAND" ><DD ><P >This parameter specifies the command to be - executed on the server host in order to pause the printerqueue.</P + executed on the server host in order to pause the printer queue.</P ><P >This command should be a program or script which takes - a printer name as its only parameter and stops the printerqueue, + a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer.</P ><P >This command is not supported by Windows for Workgroups, - but can be issued from the Printer's window under Windows 95 + but can be issued from the Printers window under Windows 95 and NT.</P ><P >If a <TT @@ -14085,7 +14152,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command. </P ><P @@ -14116,7 +14183,7 @@ NAME="QUEUERESUMECOMMAND" ><DD ><P >This parameter specifies the command to be - executed on the server host in order to resume the printerqueue. It + 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 previous parameter (<A HREF="#QUEUEPAUSECOMMAND" @@ -14129,11 +14196,11 @@ CLASS="PARAMETER" >).</P ><P >This command should be a program or script which takes - a printer name as its only parameter and resumes the printerqueue, + a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer.</P ><P >This command is not supported by Windows for Workgroups, - but can be issued from the Printer's window under Windows 95 + but can be issued from the Printers window under Windows 95 and NT.</P ><P >If a <TT @@ -14141,7 +14208,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P ><P @@ -14370,7 +14437,10 @@ CLASS="COMMAND" 192.168.4.255/STAFF</B ></P ><P ->the above line would cause nmbd to announce itself +>the above line would cause <B +CLASS="COMMAND" +>nmbd</B +> to announce itself to the two given IP addresses using the given workgroup names. If you leave out the workgroup name then the one given in the <A @@ -14415,10 +14485,10 @@ HREF="nmbd.8.html" TARGET="_top" >nmbd(8)</A > to periodically request - synchronization of browse lists with the master browser of a samba + synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This - is done in a manner that does not work with any non-samba servers.</P + is done in a manner that does not work with any non-Samba servers.</P ><P >This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse @@ -14445,7 +14515,7 @@ CLASS="COMMAND" of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it - is in fact the browse master on it's segment.</P + is in fact the browse master on its segment.</P ><P >Default: <B CLASS="COMMAND" @@ -14460,12 +14530,18 @@ NAME="RESTRICTACLWITHMASK" >restrict acl with mask (S)</DT ><DD ><P ->This is a boolean parameter. If set to false (default), then - Creation of files with access control lists (ACLS) and modification of ACLs +>This is a boolean parameter. If set to <TT +CLASS="CONSTANT" +>false</TT +> (default), then + creation of files with access control lists (ACLS) and modification of ACLs using the Windows NT/2000 ACL editor will be applied directly to the file or directory.</P ><P ->If set to True, then all requests to set an ACL on a file will have the +>If set to <TT +CLASS="CONSTANT" +>true</TT +>, then all requests to set an ACL on a file will have the parameters <A HREF="#CREATEMASK" ><TT @@ -14556,10 +14632,16 @@ NAME="RESTRICTANONYMOUS" >restrict anonymous (G)</DT ><DD ><P ->This is a boolean parameter. If it is true, then +>This is a boolean parameter. If it is <TT +CLASS="CONSTANT" +>true</TT +>, then anonymous access to the server will be restricted, namely in the case where the server is expecting the client to send a username, - but it doesn't. Setting it to true will force these anonymous + but it doesn't. Setting it to <TT +CLASS="CONSTANT" +>true</TT +> will force these anonymous connections to be denied, and the client will be required to always supply a username and password when connecting. Use of this parameter is only recommended for homogeneous NT client environments.</P @@ -14569,10 +14651,13 @@ NAME="RESTRICTANONYMOUS" likes to use anonymous connections when refreshing the share list, and this is a way to work around that.</P ><P ->When restrict anonymous is true, all anonymous connections +>When restrict anonymous is <TT +CLASS="CONSTANT" +>true</TT +>, all anonymous connections are denied no matter what they are for. This can effect the ability - of a machine to access the samba Primary Domain Controller to revalidate - it's machine account after someone else has logged on the client + of a machine to access the Samba Primary Domain Controller to revalidate + its machine account after someone else has logged on the client interactively. The NT client will display a message saying that the machine's account in the domain doesn't exist or the password is bad. The best way to deal with this is to reboot NT client machines @@ -14629,7 +14714,7 @@ NAME="ROOTDIRECTORY" CLASS="COMMAND" >chroot()</B > (i.e. - Change it's root directory) to this directory on startup. This is + Change its root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the server will deny access to files not in one of the service entries. It may also check for, and deny access to, soft links to other @@ -14703,7 +14788,7 @@ CLASS="PARAMETER" > parameter except that the command is run as root. This is useful for unmounting filesystems - (such as cdroms) after a connection is closed.</P + (such as CDROMs) after a connection is closed.</P ><P >See also <A HREF="#POSTEXEC" @@ -14735,8 +14820,8 @@ CLASS="PARAMETER" ></TT > parameter except that the command is run as root. This - is useful for mounting filesystems (such as cdroms) after a - connection is closed.</P + is useful for mounting filesystems (such as CDROMs) when a + connection is opened.</P ><P >See also <A HREF="#PREEXEC" @@ -14916,7 +15001,7 @@ NAME="SECURITYEQUALSSHARE" </EM ></P ><P ->When clients connect to a share level security server then +>When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with @@ -15173,7 +15258,7 @@ CLASS="FILENAME" ><P ><EM >Note</EM -> that from the clients point of +> that from the client's point of view <B CLASS="COMMAND" >security = server</B @@ -15275,7 +15360,7 @@ CLASS="CONSTANT" ><P ><EM >Note</EM -> that from the clients point +> that from the client's point of view <B CLASS="COMMAND" >security = domain</B @@ -15390,7 +15475,10 @@ NAME="SECURITYMASK" Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will - probably want to leave it set to 0777.</P + probably want to leave it set to <TT +CLASS="CONSTANT" +>0777</TT +>.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -15441,7 +15529,7 @@ NAME="SERVERSTRING" printer comment box in print manager and next to the IPC connection in <B CLASS="COMMAND" ->net view"</B +>net view</B >. It can be any string that you wish to show to your users.</P ><P @@ -15622,7 +15710,7 @@ CLASS="PARAMETER" >printer admin</I ></TT > group), the OpenPrinterEx() - call fails and the clients another open call with a request for + call fails and the client makes another open call with a request for a lower privilege level. This should succeed, however the APW icon will not be displayed.</P ><P @@ -15705,7 +15793,7 @@ NAME="SOCKETADDRESS" support multiple virtual interfaces on the one server, each with a different configuration.</P ><P ->By default samba will accept connections on any +>By default Samba will accept connections on any address.</P ><P >Example: <B @@ -15915,8 +16003,8 @@ CLASS="COMMAND" it is set to <TT CLASS="CONSTANT" >no</TT ->, the SSL enabled samba behaves - exactly like the non-SSL samba. If set to <TT +>, the SSL-enabled Samba behaves + exactly like the non-SSL Samba. If set to <TT CLASS="CONSTANT" >yes</TT >, @@ -15969,7 +16057,7 @@ CLASS="COMMAND" ><P >This variable defines where to look up the Certification Authorities. The given directory should contain one file for - each CA that samba will trust. The file name must be the hash + each CA that Samba will trust. The file name must be the hash value over the "Distinguished Name" of the CA. How this directory is set up is explained later in this document. All files within the directory that don't fit into this naming scheme are ignored. You @@ -16197,8 +16285,8 @@ CLASS="COMMAND" > enabled by default in any current binary version of Samba.</P ><P ->These two variables define whether samba will go - into SSL mode or not. If none of them is defined, samba will +>These two variables define whether Samba will go + into SSL mode or not. If none of them is defined, Samba will allow only SSL connections. If the <A HREF="#SSLHOSTS" > <TT @@ -16215,7 +16303,9 @@ CLASS="PARAMETER" > ssl hosts resign</I ></TT > variable lists hosts, only these - hosts will NOT be forced into SSL mode. The syntax for these two + hosts will <EM +>NOT</EM +> be forced into SSL mode. The syntax for these two variables is the same as for the <A HREF="#HOSTSALLOW" ><TT @@ -16585,7 +16675,7 @@ CLASS="CONSTANT" > the server does file lock checks only when the client explicitly asks for them.</P ><P ->Well behaved clients always ask for lock checks when it +>Well-behaved clients always ask for lock checks when it is important, so in the vast majority of cases <B CLASS="COMMAND" >strict @@ -16614,7 +16704,11 @@ NAME="STRICTSYNC" CLASS="CONSTANT" >no</TT > (the - default) means that smbd ignores the Windows applications requests for + default) means that <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> 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 @@ -16662,10 +16756,16 @@ NAME="SYNCALWAYS" ><P >This is a boolean parameter that controls whether writes will always be written to stable storage before - the write call returns. If this is false then the server will be + the write call returns. If this is <TT +CLASS="CONSTANT" +>false</TT +> then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous). - If this is true then every write will be followed by a <B + If this is <TT +CLASS="CONSTANT" +>true</TT +> then every write will be followed by a <B CLASS="COMMAND" >fsync() </B @@ -16882,7 +16982,11 @@ NAME="TOTALPRINTJOBS" >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 smbd will return an + by a client which will exceed this number, then <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> 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 @@ -16918,7 +17022,10 @@ NAME="UNIXPASSWORDSYNC" >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. - If this is set to true the program specified in the <TT + If this is set to <TT +CLASS="CONSTANT" +>true</TT +> the program specified in the <TT CLASS="PARAMETER" ><I >passwd @@ -16928,7 +17035,7 @@ CLASS="PARAMETER" >AS ROOT</EM > - to allow the new UNIX password to be set without access to the - old UNIX password (as the SMB password has change code has no + old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new).</P ><P >See also <A @@ -17017,8 +17124,11 @@ NAME="USERHOSTS" >use rhosts (G)</DT ><DD ><P ->If this global parameter is a true, it specifies - that the UNIX users <TT +>If this global parameter is <TT +CLASS="CONSTANT" +>true</TT +>, it specifies + that the UNIX user's <TT CLASS="FILENAME" >.rhosts</TT > file in their home directory @@ -17143,7 +17253,7 @@ CLASS="PARAMETER" > parameter.</P ><P >If any of the usernames begin with a '@' then the name - will be looked up first in the yp netgroups list (if Samba + will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name.</P @@ -17153,7 +17263,7 @@ CLASS="PARAMETER" expand to a list of all users in the group of that name.</P ><P >If any of the usernames begin with a '&'then the name - will be looked up only in the yp netgroups database (if Samba + 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.</P ><P @@ -17379,7 +17489,10 @@ NAME="UTMP" Samba has been configured and compiled with the option <B CLASS="COMMAND" > --with-utmp</B ->. If set to True then Samba will attempt +>. If set to <TT +CLASS="CONSTANT" +>true</TT +> then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the user connecting to a Samba share.</P @@ -17780,7 +17893,7 @@ NAME="VFSOPTIONS" ><DD ><P >This parameter allows parameters to be passed - to the vfs layer at initialisation time. The Samba VFS layer + to the vfs layer at initialization time. The Samba VFS layer is new to Samba 2.2 and must be enabled at compile time with --with-vfs. See also <A HREF="#VFSOBJECT" @@ -17877,7 +17990,7 @@ HREF="winbindd.8.html" TARGET="_top" > winbindd(8)</A > daemon. This range of group ids should have no - existing local or nis groups within it as strange conflicts can + existing local or NIS groups within it as strange conflicts can occur otherwise.</P ><P >Default: <B @@ -17954,7 +18067,7 @@ HREF="winbindd.8.html" TARGET="_top" > winbindd(8)</A > daemon. This range of ids should have no - existing local or nis users within it as strange conflicts can + existing local or NIS users within it as strange conflicts can occur otherwise.</P ><P >Default: <B @@ -18003,14 +18116,14 @@ CLASS="COMMAND" ></LI ><LI ><P ->The second argument is the netbios name. If the +>The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores and periods.</P ></LI ><LI ><P ->The third argument is the netbios name +>The third argument is the NetBIOS name type as a 2 digit hexadecimal number. </P ></LI ><LI @@ -18108,14 +18221,20 @@ TARGET="_top" > nmbd(8)</A > process in Samba will act as a WINS server. You should - not set this to true unless you have a multi-subnetted network and + not set this to <TT +CLASS="CONSTANT" +>true</TT +> unless you have a multi-subnetted network and you wish a particular <B CLASS="COMMAND" >nmbd</B > to be your WINS server. Note that you should <EM >NEVER</EM -> set this to true +> set this to <TT +CLASS="CONSTANT" +>true</TT +> on more than one machine in your network.</P ><P >Default: <B @@ -18187,7 +18306,7 @@ NAME="WRITECACHESIZE" within it.</P ><P >This cache allows Samba to batch client writes into a more - efficient write size for RAID disks (ie. writes may be tuned to + efficient write size for RAID disks (i.e. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs.</P @@ -18279,7 +18398,7 @@ NAME="WRITERAW" ><DD ><P >This parameter controls whether or not the server - will support raw writes SMB's when transferring data from clients. + will support raw write SMB's when transferring data from clients. You should never need to change this parameter.</P ><P >Default: <B @@ -18331,7 +18450,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5791" +NAME="AEN5828" ></A ><H2 >WARNINGS</H2 @@ -18361,7 +18480,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5797" +NAME="AEN5834" ></A ><H2 >VERSION</H2 @@ -18372,7 +18491,7 @@ NAME="AEN5797" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5800" +NAME="AEN5837" ></A ><H2 >SEE ALSO</H2 @@ -18451,7 +18570,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5820" +NAME="AEN5857" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index b8323dd8f5b..637720fa6ba 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -52,18 +52,24 @@ TARGET="_top" > Samba</A > suite.</P ><P ->The smbcacls program manipulates NT Access Control Lists +>The <B +CLASS="COMMAND" +>smbcacls</B +> program manipulates NT Access Control Lists (ACLs) on SMB file shares. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN27" +NAME="AEN28" ></A ><H2 >OPTIONS</H2 ><P ->The following options are available to the smbcacls program. +>The following options are available to the <B +CLASS="COMMAND" +>smbcacls</B +> program. The format of ACLs is described in the section ACL FORMAT </P ><P ></P @@ -90,7 +96,7 @@ CLASS="VARIABLELIST" >-D acls</DT ><DD ><P ->Delete any ACLs specfied on the command line. +>Delete any ACLs specified on the command line. An error will be printed for each ACL specified that was not already present in the ACL list. </P ></DD @@ -175,7 +181,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN73" +NAME="AEN75" ></A ><H2 >ACL FORMAT</H2 @@ -322,7 +328,7 @@ ACL:<sid or name>:<type>/<flags>/<mask> ><DIV CLASS="REFSECT1" ><A -NAME="AEN123" +NAME="AEN125" ></A ><H2 >EXIT STATUS</H2 @@ -334,8 +340,11 @@ CLASS="COMMAND" depending on the success or otherwise of the operations performed. The exit status may be one of the following values. </P ><P ->If the operation succeded, smbcacls returns and exit - status of 0. If smbcacls couldn't connect to the specified server, +>If the operation succeeded, smbcacls returns and exit + status of 0. If <B +CLASS="COMMAND" +>smbcacls</B +> couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned. If there was an error parsing any command line arguments, an exit status of 2 is returned. </P @@ -343,7 +352,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN128" +NAME="AEN131" ></A ><H2 >VERSION</H2 @@ -354,7 +363,7 @@ NAME="AEN128" ><DIV CLASS="REFSECT1" ><A -NAME="AEN131" +NAME="AEN134" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 8232906680f..f38ae269951 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -121,8 +121,14 @@ CLASS="PARAMETER" ><I >-R</I ></TT -> parameter to smbclient or - using the name resolve order parameter in the smb.conf file, +> parameter to <B +CLASS="COMMAND" +>smbclient</B +> or + using the name resolve order parameter in the <TT +CLASS="FILENAME" +>smb.conf</TT +> file, allowing an administrator to change the order and methods by which server names are looked up. </P ></DD @@ -194,7 +200,7 @@ CLASS="FILENAME" ><P >This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve - host names to IP addresses. The option takes a space separated + host names to IP addresses. The option takes a space-separated string of different name resolution options.</P ><P >The options are :"lmhosts", "host", "wins" and "bcast". They @@ -227,7 +233,7 @@ CLASS="FILENAME" >/etc/hosts </TT >, NIS, or DNS lookups. This method of name resolution - is operating system depended for instance on IRIX or Solaris this + is operating system dependent, for instance on IRIX or Solaris this may be controlled by the <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -284,7 +290,10 @@ CLASS="PARAMETER" >name resolve order </I ></TT -> parameter of the smb.conf file the name resolution +> parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT +> file the name resolution methods will be attempted in this order. </P ></DD ><DT @@ -351,7 +360,13 @@ CLASS="FILENAME" ><P >This specifies a NetBIOS scope that smbclient will use to communicate with when generating NetBIOS names. For details - on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. + on the use of NetBIOS scopes, see <TT +CLASS="FILENAME" +>rfc1001.txt</TT +> and <TT +CLASS="FILENAME" +>rfc1002.txt</TT +>. NetBIOS scopes are <EM >very</EM > rarely used, only set @@ -383,7 +398,12 @@ CLASS="FILENAME" >-d debuglevel</DT ><DD ><P ->debuglevel is an integer from 0 to 10, or +><TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is an integer from 0 to 10, or the letter 'A'. </P ><P >The default value if this parameter is not specified @@ -400,7 +420,12 @@ CLASS="FILENAME" data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely - cryptic. If debuglevel is set to the letter 'A', then <EM + cryptic. If <TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is set to the letter 'A', then <EM >all </EM > debug messages will be printed. This setting @@ -410,9 +435,9 @@ CLASS="FILENAME" to know how the code works internally). </P ><P >Note that specifying this parameter here will override - the log level parameter in the <B -CLASS="COMMAND" ->smb.conf (5)</B + the log level parameter in the <TT +CLASS="FILENAME" +>smb.conf (5)</TT > file. </P ></DD @@ -429,7 +454,12 @@ CLASS="COMMAND" >-l logfilename</DT ><DD ><P ->If specified, logfilename specifies a base filename +>If specified, <TT +CLASS="REPLACEABLE" +><I +>logfilename</I +></TT +> specifies a base filename into which operational data from the running client will be logged. </P ><P @@ -455,7 +485,12 @@ CLASS="FILENAME" >-I IP-address</DT ><DD ><P ->IP address is the address of the server to connect to. +><TT +CLASS="REPLACEABLE" +><I +>IP address</I +></TT +> is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation. </P ><P >Normally the client would attempt to locate a named @@ -492,35 +527,37 @@ CLASS="PARAMETER" ><P >Sets the SMB username or username and password. If %pass is not specified, The user will be prompted. The client - will first check the USER environment variable, then the + will first check the <TT +CLASS="ENVAR" +>USER</TT +> environment variable, then the <TT -CLASS="PARAMETER" -><I ->$LOGNAME</I -></TT -> variable and if either exist, the +CLASS="ENVAR" +>LOGNAME</TT +> variable and if either exists, the string is uppercased. Anything in these variables following a '%' - sign will be treated as the password. If these environmental + sign will be treated as the password. If these environment variables are not found, the username <TT CLASS="CONSTANT" >GUEST</TT > is used. </P ><P ->If the password is not included in these environment - variables (using the %pass syntax), rpcclient will look for +>If the password is not included in these environment + variables (using the %pass syntax), <B +CLASS="COMMAND" +>rpcclient</B +> will look for a <TT -CLASS="PARAMETER" -><I ->$PASSWD</I -></TT +CLASS="ENVAR" +>PASSWD</TT > environment variable from which to read the password. </P ><P >A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin doesn't - desire to pass the credentials on the command line or via environment + wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the <TT @@ -532,10 +569,8 @@ CLASS="PARAMETER" ><P >Be cautious about including passwords in scripts or in the <TT -CLASS="PARAMETER" -><I ->$PASSWD</I -></TT +CLASS="ENVAR" +>PASSWD</TT > environment variable. Also, on many systems the command line of a running process may be seen via the <B @@ -592,14 +627,17 @@ CLASS="PARAMETER" </I ></TT > option may be useful if your NetBIOS names don't - match your tcp/ip dns host names or if you are trying to reach a + match your TCP/IP DNS host names or if you are trying to reach a host on another network. </P ></DD ><DT >-t terminal code</DT ><DD ><P ->This option tells smbclient how to interpret +>This option tells <B +CLASS="COMMAND" +>smbclient</B +> how to interpret filenames coming from the remote server. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (<EM @@ -771,7 +809,7 @@ CLASS="PARAMETER" >r</I ></TT > - Regular expression include - or exclude. Uses regular regular expression matching for + or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. @@ -829,7 +867,10 @@ CLASS="COMMAND" >'s tar option now supports long file names both on backup and restore. However, the full path name of the file must be less than 1024 bytes. Also, when - a tar archive is created, smbclient's tar option places all + a tar archive is created, <B +CLASS="COMMAND" +>smbclient</B +>'s tar option places all files in the archive with relative names, not absolute names. </P ><P @@ -845,12 +886,15 @@ CLASS="COMMAND" >Examples</EM ></P ><P ->Restore from tar file backup.tar into myshare on mypc +>Restore from tar file <TT +CLASS="FILENAME" +>backup.tar</TT +> into myshare on mypc (no password on share). </P ><P ><B CLASS="COMMAND" ->smbclient //mypc/myshare "" -N -Tx backup.tar +>smbclient //mypc/yshare "" -N -Tx backup.tar </B ></P ><P @@ -906,7 +950,7 @@ CLASS="COMMAND" >-c command string</DT ><DD ><P ->command string is a semicolon separated list of +>command string is a semicolon-separated list of commands to be executed instead of prompting from stdin. <TT CLASS="PARAMETER" ><I @@ -931,7 +975,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN297" +NAME="AEN311" ></A ><H2 >OPERATIONS</H2 @@ -979,7 +1023,12 @@ CLASS="VARIABLELIST" >? [command]</DT ><DD ><P ->If "command" is specified, the ? command will display +>If <TT +CLASS="REPLACEABLE" +><I +>command</I +></TT +> is specified, the ? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will be displayed. </P @@ -988,7 +1037,12 @@ CLASS="VARIABLELIST" >! [shell command]</DT ><DD ><P ->If "shell command" is specified, the ! +>If <TT +CLASS="REPLACEABLE" +><I +>shell command</I +></TT +> is specified, the ! command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run. </P @@ -1010,14 +1064,24 @@ CLASS="VARIABLELIST" ><DD ><P >The client will request that the server attempt - to delete all files matching "mask" from the current working + to delete all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> from the current working directory on the server. </P ></DD ><DT >dir <mask></DT ><DD ><P ->A list of the files matching "mask" in the current +>A list of the files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> in the current working directory on the server will be retrieved from the server and displayed. </P ></DD @@ -1032,9 +1096,15 @@ CLASS="VARIABLELIST" >get <remote file name> [local file name]</DT ><DD ><P ->Copy the file called "remote file name" from +>Copy the file called <TT +CLASS="FILENAME" +>remote file name</TT +> from the server to the machine running the client. If specified, name - the local copy "local file name". Note that all transfers in + the local copy <TT +CLASS="FILENAME" +>local file name</TT +>. Note that all transfers in <B CLASS="COMMAND" >smbclient</B @@ -1051,7 +1121,12 @@ CLASS="COMMAND" >lcd [directory name]</DT ><DD ><P ->If "directory name" is specified, the current +>If <TT +CLASS="REPLACEABLE" +><I +>directory name</I +></TT +> is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. </P @@ -1114,13 +1189,26 @@ CLASS="COMMAND" >mget <mask></DT ><DD ><P ->Copy all files matching mask from the server to +>Copy all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> from the server to the machine running the client. </P ><P ->Note that mask is interpreted differently during recursive +>Note that <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in - smbclient are binary. See also the lowercase command. </P + <B +CLASS="COMMAND" +>smbclient</B +> are binary. See also the lowercase command. </P ></DD ><DT >mkdir <directory name></DT @@ -1133,13 +1221,26 @@ CLASS="COMMAND" >mput <mask></DT ><DD ><P ->Copy all files matching mask in the current working +>Copy all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> in the current working directory on the local machine to the current working directory on the server. </P ><P ->Note that mask is interpreted differently during recursive +>Note that <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask - commands for more information. Note that all transfers in smbclient + commands for more information. Note that all transfers in <B +CLASS="COMMAND" +>smbclient</B +> are binary. </P ></DD ><DT @@ -1175,10 +1276,19 @@ CLASS="COMMAND" >put <local file name> [remote file name]</DT ><DD ><P ->Copy the file called "local file name" from the +>Copy the file called <TT +CLASS="FILENAME" +>local file name</TT +> from the machine running the client to the server. If specified, - name the remote copy "remote file name". Note that all transfers - in smbclient are binary. See also the lowercase command. + name the remote copy <TT +CLASS="FILENAME" +>remote file name</TT +>. Note that all transfers + in <B +CLASS="COMMAND" +>smbclient</B +> are binary. See also the lowercase command. </P ></DD ><DT @@ -1223,7 +1333,12 @@ CLASS="COMMAND" >rm <mask></DT ><DD ><P ->Remove all files matching mask from the current +>Remove all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> from the current working directory on the server. </P ></DD ><DT @@ -1255,7 +1370,12 @@ CLASS="PARAMETER" ><P >Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in - blocksize*TBLOCK (usually 512 byte) blocks. </P + <TT +CLASS="REPLACEABLE" +><I +>blocksize</I +></TT +>*TBLOCK (usually 512 byte) blocks. </P ></DD ><DT >tarmode <full|inc|reset|noreset></DT @@ -1288,7 +1408,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN446" +NAME="AEN478" ></A ><H2 >NOTES</H2 @@ -1309,26 +1429,22 @@ NAME="AEN446" ><DIV CLASS="REFSECT1" ><A -NAME="AEN451" +NAME="AEN483" ></A ><H2 >ENVIRONMENT VARIABLES</H2 ><P >The variable <TT -CLASS="PARAMETER" -><I ->$USER</I -></TT +CLASS="ENVAR" +>USER</TT > may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.</P ><P >The variable <TT -CLASS="PARAMETER" -><I ->$PASSWD</I -></TT +CLASS="ENVAR" +>PASSWD</TT > may contain the password of the person using the client. This information is used only if the protocol level is high enough to support @@ -1337,7 +1453,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN457" +NAME="AEN489" ></A ><H2 >INSTALLATION</H2 @@ -1368,14 +1484,14 @@ CLASS="FILENAME" CLASS="COMMAND" >smbd(8) </B -> an ordinary user - running that server as a daemon +> 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. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN467" +NAME="AEN499" ></A ><H2 >DIAGNOSTICS</H2 @@ -1391,7 +1507,7 @@ NAME="AEN467" ><DIV CLASS="REFSECT1" ><A -NAME="AEN471" +NAME="AEN503" ></A ><H2 >VERSION</H2 @@ -1402,7 +1518,7 @@ NAME="AEN471" ><DIV CLASS="REFSECT1" ><A -NAME="AEN474" +NAME="AEN506" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 35520b05afc..7096dc205f7 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -98,12 +98,15 @@ CLASS="FILENAME" can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to - disconnect from the service, or smbd killed and restarted.</P + disconnect from the service, or <B +CLASS="COMMAND" +>smbd</B +> killed and restarted.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN35" +NAME="AEN36" ></A ><H2 >OPTIONS</H2 @@ -120,9 +123,12 @@ CLASS="VARIABLELIST" the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a - daemon is the recommended way of running smbd for + daemon is the recommended way of running <B +CLASS="COMMAND" +>smbd</B +> for servers that provide more than casual use file and - print services. This switch is assumed is <B + print services. This switch is assumed if <B CLASS="COMMAND" >smbd </B @@ -153,7 +159,10 @@ CLASS="COMMAND" >-P</DT ><DD ><P ->Passive option. Causes smbd not to +>Passive option. Causes <B +CLASS="COMMAND" +>smbd</B +> not to send any network traffic out. Used for debugging by the developers only.</P ></DD @@ -181,7 +190,12 @@ CLASS="COMMAND" >-d <debug level></DT ><DD ><P ->debuglevel is an integer +><TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P ><P @@ -217,8 +231,11 @@ CLASS="FILENAME" >-l <log file></DT ><DD ><P ->If specified, <EM ->log file</EM +>If specified, <TT +CLASS="REPLACEABLE" +><I +>log file</I +></TT > specifies a log filename into which informational and debug messages from the running server will be logged. The log @@ -261,7 +278,12 @@ CLASS="FILENAME" >-p <port number></DT ><DD ><P ->port number is a positive integer +><TT +CLASS="REPLACEABLE" +><I +>port number</I +></TT +> is a positive integer value. The default value if this parameter is not specified is 139.</P ><P @@ -309,7 +331,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN109" ></A ><H2 >FILES</H2 @@ -407,7 +429,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN137" +NAME="AEN142" ></A ><H2 >LIMITATIONS</H2 @@ -426,7 +448,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN141" +NAME="AEN146" ></A ><H2 >ENVIRONMENTVARIABLES</H2 @@ -436,12 +458,18 @@ NAME="AEN141" CLASS="VARIABLELIST" ><DL ><DT ->PRINTER</DT +><TT +CLASS="ENVAR" +>PRINTER</TT +></DT ><DD ><P >If no printer name is specified to printable services, most systems will use the value of - this variable (or lp if this variable is + this variable (or <TT +CLASS="CONSTANT" +>lp</TT +> if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.</P ></DD @@ -451,7 +479,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN148" +NAME="AEN155" ></A ><H2 >INSTALLATION</H2 @@ -469,10 +497,16 @@ CLASS="FILENAME" program itself should be executable by all, as users may wish to run the server themselves (in which case it will of course run with their privileges). The server should NOT be setuid. On some - systems it may be worthwhile to make smbd setgid to an empty group. + systems it may be worthwhile to make <B +CLASS="COMMAND" +>smbd</B +> setgid to an empty group. This is because some systems may have a security hole where daemon processes that become a user can be attached to with a debugger. - Making the smbd file setgid to an empty group may prevent + Making the <B +CLASS="COMMAND" +>smbd</B +> file setgid to an empty group may prevent this hole from being exploited. This security hole and the suggested fix has only been confirmed on old versions (pre-kernel 2.0) of Linux at the time this was written. It is possible that this hole only @@ -567,7 +601,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN179" +NAME="AEN188" ></A ><H2 >RUNNING THE SERVER AS A DAEMON</H2 @@ -622,7 +656,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN192" +NAME="AEN201" ></A ><H2 >RUNNING THE SERVER ON REQUEST</H2 @@ -631,7 +665,10 @@ NAME="AEN192" CLASS="COMMAND" >inetd </B ->, you can arrange to have the smbd server started +>, you can arrange to have the <B +CLASS="COMMAND" +>smbd</B +> server started whenever a process attempts to connect to it. This requires several changes to the startup files on the host machine. If you are experimenting as an ordinary user rather than as root, you will @@ -755,7 +792,7 @@ CLASS="COMPUTEROUTPUT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN223" +NAME="AEN233" ></A ><H2 >TESTING THE INSTALLATION</H2 @@ -769,8 +806,18 @@ CLASS="COMMAND" > will reread their configuration tables if they receive a HUP signal.</P ><P ->If your machine's name is fred and your - name is mary, you should now be able to connect +>If your machine's name is <TT +CLASS="REPLACEABLE" +><I +>fred</I +></TT +> and your + name is <TT +CLASS="REPLACEABLE" +><I +>mary</I +></TT +>, you should now be able to connect to the service <TT CLASS="FILENAME" >\\fred\mary</TT @@ -803,7 +850,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN235" +NAME="AEN247" ></A ><H2 >VERSION</H2 @@ -814,7 +861,7 @@ NAME="AEN235" ><DIV CLASS="REFSECT1" ><A -NAME="AEN238" +NAME="AEN250" ></A ><H2 >DIAGNOSTICS</H2 @@ -837,19 +884,25 @@ NAME="AEN238" ><DIV CLASS="REFSECT1" ><A -NAME="AEN243" +NAME="AEN255" ></A ><H2 >SIGNALS</H2 ><P ->Sending the smbd a SIGHUP will cause it to - re-load its <TT +>Sending the <B +CLASS="COMMAND" +>smbd</B +> a SIGHUP will cause it to + reload its <TT CLASS="FILENAME" >smb.conf</TT > configuration file within a short period of time.</P ><P ->To shut down a users smbd process it is recommended +>To shut down a user's <B +CLASS="COMMAND" +>smbd</B +> process it is recommended that <B CLASS="COMMAND" >SIGKILL (-9)</B @@ -858,10 +911,16 @@ CLASS="COMMAND" > be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate - an smbd is to send it a SIGTERM (-15) signal and wait for + an <B +CLASS="COMMAND" +>smbd</B +> is to send it a SIGTERM (-15) signal and wait for it to die on its own.</P ><P ->The debug log level of smbd may be raised by sending +>The debug log level of <B +CLASS="COMMAND" +>smbd</B +> may be raised by sending it a SIGUSR1 (<B CLASS="COMMAND" >kill -USR1 <smbd-pid></B @@ -874,8 +933,14 @@ CLASS="COMMAND" whilst still running at a normally low log level.</P ><P >Note that as the signal handlers send a debug write, - they are not re-entrant in smbd. This you should wait until - smbd is in a state of waiting for an incoming smb before + they are not re-entrant in <B +CLASS="COMMAND" +>smbd</B +>. This you should wait until + <B +CLASS="COMMAND" +>smbd</B +> is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance.</P @@ -883,7 +948,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN254" +NAME="AEN272" ></A ><H2 >SEE ALSO</H2 @@ -949,7 +1014,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN271" +NAME="AEN289" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index e083cfd3bad..6546b7c7070 100644 --- a/docs/htmldocs/smbmnt.8.html +++ b/docs/htmldocs/smbmnt.8.html @@ -55,7 +55,7 @@ CLASS="COMMAND" CLASS="COMMAND" >smbmnt</B > is meant to be installed setuid root - so that normal users can mount their smb shares. It checks + so that normal users can mount their SMB shares. It checks whether the user has write permissions on the mount point and then mounts the directory.</P ><P @@ -125,7 +125,7 @@ CLASS="VARIABLELIST" ><DD ><P > list of options that are passed as-is to smbfs, if this - command is run on a 2.4 or higher linux kernel. + command is run on a 2.4 or higher Linux kernel. </P ></DD ></DL diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index 4642dfe8910..721397312ae 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -60,17 +60,29 @@ CLASS="COMMAND" > command when using the "-t smb" option. The kernel must support the smbfs filesystem. </P ><P ->Options to smbmount are specified as a comma separated +>Options to <B +CLASS="COMMAND" +>smbmount</B +> are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that smbfs supports them. If you get mount failures, check your kernel log for errors on unknown options.</P ><P ->smbmount is a daemon. After mounting it keeps running until +><B +CLASS="COMMAND" +>smbmount</B +> 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 log.smbmount. The - smbmount process may also be called mount.smbfs.</P + typically this output will end up in <TT +CLASS="FILENAME" +>log.smbmount</TT +>. The + <B +CLASS="COMMAND" +>smbmount</B +> process may also be called mount.smbfs.</P ><P ><EM >NOTE:</EM @@ -91,7 +103,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN27" +NAME="AEN31" ></A ><H2 >OPTIONS</H2 @@ -162,7 +174,10 @@ CLASS="PROGRAMLISTING" </P ><P >This is preferred over having passwords in plaintext in a - shared file, such as /etc/fstab. Be sure to protect any + shared file, such as <TT +CLASS="FILENAME" +>/etc/fstab</TT +>. Be sure to protect any credentials file properly. </P ></DD @@ -210,7 +225,7 @@ CLASS="PROGRAMLISTING" >dmask=<arg></DT ><DD ><P ->sets the directory mask. This deterines the +>sets the directory mask. This determines the permissions that remote directories have in the local filesystem. The default is based on the current umask. </P ></DD @@ -282,7 +297,7 @@ CLASS="PARAMETER" >iocharset=<arg></DT ><DD ><P -> sets the charset used by the linux side for codepage +> sets the charset used by the Linux side for codepage to charset translations (NLS). Argument should be the name of a charset, like iso8859-1. (Note: only kernel 2.4.0 or later) @@ -318,7 +333,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN120" +NAME="AEN125" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -345,12 +360,12 @@ CLASS="ENVAR" >PASSWD_FILE</TT > may contain the pathname of a file to read the password from. A single line of input is - read and used as password.</P + read and used as the password.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN128" +NAME="AEN133" ></A ><H2 >BUGS</H2 @@ -370,7 +385,7 @@ NAME="AEN128" ></LI ></UL ><P ->Note that the typical response to a bugreport is suggestion +>Note that the typical response to a bug report is suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)</P @@ -378,7 +393,7 @@ NAME="AEN128" ><DIV CLASS="REFSECT1" ><A -NAME="AEN135" +NAME="AEN140" ></A ><H2 >SEE ALSO</H2 @@ -389,7 +404,7 @@ NAME="AEN135" ><DIV CLASS="REFSECT1" ><A -NAME="AEN138" +NAME="AEN143" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 7de54f63092..1f862b66114 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -101,9 +101,9 @@ CLASS="VARIABLELIST" >Lanman Password Hash</DT ><DD ><P ->This is the LANMAN hash of the users password, +>This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES - encrypting a well known string with the users password as the + encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the @@ -111,7 +111,7 @@ CLASS="VARIABLELIST" is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to - 32 'X' characters then the users account is marked as + 32 'X' characters then the user's account is marked as <TT CLASS="CONSTANT" >disabled</TT @@ -140,14 +140,14 @@ CLASS="CONSTANT" >NT Password Hash</DT ><DD ><P ->This is the Windows NT hash of the users +>This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is - created by taking the users password as represented in + created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it. </P ><P >This password hash is considered more secure than - the Lanman Password Hash as it preserves the case of the + the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is @@ -198,7 +198,7 @@ CLASS="CONSTANT" ><EM >N</EM > - This means the - account has no password (the passwords in the fields Lanman + account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the <TT CLASS="PARAMETER" diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 1c4df519414..f48754163b9 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -24,7 +24,7 @@ NAME="AEN5" ></A ><H2 >Name</H2 ->smbpasswd -- change a users SMB password</DIV +>smbpasswd -- change a user's SMB password</DIV ><DIV CLASS="REFSYNOPSISDIV" ><A @@ -61,7 +61,7 @@ TARGET="_top" SMB passwords. </P ><P >By default (when run with no arguments) it will attempt to - change the current users SMB password on the local machine. This is + change the current user's SMB password on the local machine. This is similar to the way the <B CLASS="COMMAND" >passwd(1)</B @@ -86,10 +86,10 @@ CLASS="FILENAME" > file. </P ><P >When run by an ordinary user with no options. smbpasswd - will prompt them for their old smb password and then ask them + will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen - whilst being typed. If you have a blank smb password (specified by + whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password. </P ><P @@ -167,7 +167,7 @@ CLASS="CONSTANT" will fail. </P ><P >If the smbpasswd file is in the 'old' format (pre-Samba 2.0 - format) there is no space in the users password entry to write + format) there is no space in the user's password entry to write this information and so the user is disabled by writing 'X' characters into the password space in the smbpasswd file. See <B CLASS="COMMAND" @@ -217,7 +217,7 @@ CLASS="COMMAND" ><DD ><P ><TT -CLASS="PARAMETER" +CLASS="REPLACEABLE" ><I >debuglevel</I ></TT @@ -500,7 +500,7 @@ CLASS="COMMAND" ><DD ><P >This option causes smbpasswd to be silent (i.e. - not issue prompts) and to read it's old and new passwords from + not issue prompts) and to read its old and new passwords from standard input, rather than from <TT CLASS="FILENAME" >/dev/tty</TT diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index 3033a50ccd2..3f1b704d388 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -67,7 +67,7 @@ CLASS="COMMAND" CLASS="COMMAND" >rcp</B >. You must use a - shell that is dynmanically linked in order for <B + shell that is dynamically linked in order for <B CLASS="COMMAND" >smbsh</B > diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index f689b4a0bce..254abe9a9de 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -89,10 +89,8 @@ TARGET="_top" ><P >smbspool tries to get the URI from argv[0]. If argv[0] contains the name of the program then it looks in the <TT -CLASS="PARAMETER" -><I -> DEVICE_URI</I -></TT +CLASS="ENVAR" +> DEVICE_URI</TT > environment variable.</P ><P >Programs using the <B @@ -101,10 +99,8 @@ CLASS="COMMAND" > functions can pass the URI in argv[0], while shell scripts must set the <TT -CLASS="PARAMETER" -><I ->DEVICE_URI</I -></TT +CLASS="ENVAR" +>DEVICE_URI</TT > environment variable prior to running smbspool.</P ></DIV diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 0a26e720945..68929fd5f91 100644 --- a/docs/htmldocs/smbumount.8.html +++ b/docs/htmldocs/smbumount.8.html @@ -51,7 +51,7 @@ NAME="AEN12" CLASS="COMMAND" >smbumount</B > has - been written to give normal linux-users more control over their + been written to give normal Linux users more control over their resources. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again. For root it is not necessary to use smbumount. The normal umount diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index be16272bb68..386fe5bc7af 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -68,15 +68,24 @@ CLASS="FILENAME" CLASS="COMMAND" >swat</B > configuration page has help links - to all the configurable options in the smb.conf file allowing an + to all the configurable options in the <TT +CLASS="FILENAME" +>smb.conf</TT +> file allowing an administrator to easily look up the effects of any change. </P ><P ->swat is run from inetd </P +><B +CLASS="COMMAND" +>swat</B +> is run from <B +CLASS="COMMAND" +>inetd</B +> </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN23" +NAME="AEN26" ></A ><H2 >OPTIONS</H2 @@ -95,7 +104,10 @@ CLASS="VARIABLELIST" CLASS="COMMAND" >smbd </B -> server. This is the file that swat will modify. +> server. This is the file that <B +CLASS="COMMAND" +>swat</B +> 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. @@ -110,8 +122,14 @@ CLASS="FILENAME" ><DD ><P >This option disables authentication and puts - swat in demo mode. In that mode anyone will be able to modify - the smb.conf file. </P + <B +CLASS="COMMAND" +>swat</B +> in demo mode. In that mode anyone will be able to modify + the <TT +CLASS="FILENAME" +>smb.conf</TT +> file. </P ><P ><EM >Do NOT enable this option on a production @@ -124,7 +142,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN38" +NAME="AEN44" ></A ><H2 >INSTALLATION</H2 @@ -158,7 +176,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN50" +NAME="AEN56" ></A ><H3 >Inetd Installation</H3 @@ -171,7 +189,10 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/services</TT > - to enable SWAT to be launched via inetd.</P + to enable SWAT to be launched via <B +CLASS="COMMAND" +>inetd</B +>.</P ><P >In <TT CLASS="FILENAME" @@ -228,15 +249,15 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN71" +NAME="AEN78" ></A ><H3 >Launching</H3 ><P ->To launch swat just run your favorite web browser and +>To launch SWAT just run your favorite web browser and point it at "http://localhost:901/".</P ><P ->Note that you can attach to swat from any IP connected +>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. </P @@ -245,7 +266,7 @@ NAME="AEN71" ><DIV CLASS="REFSECT1" ><A -NAME="AEN75" +NAME="AEN82" ></A ><H2 >FILES</H2 @@ -303,7 +324,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN96" +NAME="AEN103" ></A ><H2 >WARNINGS</H2 @@ -335,7 +356,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN111" ></A ><H2 >VERSION</H2 @@ -346,7 +367,7 @@ NAME="AEN104" ><DIV CLASS="REFSECT1" ><A -NAME="AEN107" +NAME="AEN114" ></A ><H2 >SEE ALSO</H2 @@ -373,7 +394,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN114" +NAME="AEN121" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 599746e4145..bae907c687a 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -125,7 +125,12 @@ CLASS="COMMAND" >-L servername</DT ><DD ><P ->Sets the value of the %L macro to servername. +>Sets the value of the %L macro to <TT +CLASS="REPLACEABLE" +><I +>servername</I +></TT +>. This is useful for testing include files specified with the %L macro. </P ></DD @@ -146,7 +151,10 @@ CLASS="FILENAME" ><DD ><P >If this parameter and the following are - specified, then testparm will examine the <TT + specified, then <B +CLASS="COMMAND" +>testparm</B +> will examine the <TT CLASS="PARAMETER" ><I >hosts @@ -184,7 +192,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN64" +NAME="AEN66" ></A ><H2 >FILES</H2 @@ -213,13 +221,13 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN73" +NAME="AEN75" ></A ><H2 >DIAGNOSTICS</H2 ><P >The program will issue a message saying whether the - configuration file loaded OK or not. This message may be preceeded by + configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details to stdout. </P @@ -227,7 +235,7 @@ NAME="AEN73" ><DIV CLASS="REFSECT1" ><A -NAME="AEN76" +NAME="AEN78" ></A ><H2 >VERSION</H2 @@ -238,7 +246,7 @@ NAME="AEN76" ><DIV CLASS="REFSECT1" ><A -NAME="AEN79" +NAME="AEN81" ></A ><H2 >SEE ALSO</H2 @@ -264,7 +272,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN86" +NAME="AEN88" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index 2787f514c07..129d0459e1f 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -243,13 +243,16 @@ NAME="AEN88" CLASS="COMMAND" >winbindd(8) </B -> daemon is not working wbinfo will always return +> daemon is not working <B +CLASS="COMMAND" +>wbinfo</B +> will always return failure. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN92" +NAME="AEN93" ></A ><H2 >VERSION</H2 @@ -261,7 +264,7 @@ NAME="AEN92" ><DIV CLASS="REFSECT1" ><A -NAME="AEN95" +NAME="AEN96" ></A ><H2 >SEE ALSO</H2 @@ -279,7 +282,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN100" +NAME="AEN101" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index 2f023561edc..447069f17aa 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->Unifed Logons between Windows NT and UNIX using Winbind</TITLE +>Unified Logons between Windows NT and UNIX using Winbind</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD @@ -20,7 +20,7 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="AEN1" ->Unifed Logons between Windows NT and UNIX using Winbind</A +>Unified Logons between Windows NT and UNIX using Winbind</A ></H1 ><HR></DIV ><DIV @@ -39,7 +39,7 @@ CLASS="EMPHASIS" >winbind </I >, a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation + solution to the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind @@ -70,7 +70,7 @@ NAME="AEN7" can lead to synchronization problems between the UNIX and Windows systems and confusion for users.</P ><P ->We divide the unifed logon problem for UNIX machines into +>We divide the unified logon problem for UNIX machines into three smaller problems:</P ><P ></P @@ -97,7 +97,7 @@ NAME="AEN7" information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system. The winbind system provides a simple - and elegant solution to all three components of the unifed logon + and elegant solution to all three components of the unified logon problem.</P ></DIV ><DIV @@ -224,7 +224,7 @@ NAME="AEN40" >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information - to be resolved from dierent sources. For example, a standalone + to be resolved from different sources. For example, a standalone UNIX workstation may resolve system information from a series of flat files stored on the local lesystem. A networked workstation may first attempt to resolve system information from local files, @@ -253,7 +253,7 @@ CLASS="FILENAME" for a line which matches the service type being requested, for example the "passwd" service type is used when user or group names are looked up. This config line species which implementations - of that service should be tried andin what order. If the passwd + of that service should be tried and in what order. If the passwd config line is:</P ><P ><B @@ -303,7 +303,7 @@ NAME="AEN56" >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different - authentication methods for dierent system applications without + authentication methods for different system applications without having to recompile these applications. PAM is also useful for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users @@ -318,7 +318,7 @@ NAME="AEN56" this change take eect directly on the Primary Domain Controller. </P ><P ->PAM is congured by providing control files in the directory +>PAM is configured by providing control files in the directory <TT CLASS="FILENAME" >/etc/pam.d/</TT @@ -350,11 +350,11 @@ NAME="AEN64" ></H2 ><P >When a user or group is created under Windows NT - is it allocated a numerical relative identier (RID). This is - slightly dierent to UNIX which has a range of numbers which are + is it allocated a numerical relative identifier (RID). This is + slightly different to UNIX which has a range of numbers which are used to identify users, and the same range in which to identify groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is congured it is given part of the UNIX + vice versa. When winbind is configured it is given part of the UNIX user id space and a part of the UNIX group id space in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is allocated the next UNIX id from @@ -381,7 +381,7 @@ NAME="AEN68" by NT domain controllers. User or group information returned by a PDC is cached by winbind along with a sequence number also returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modied. If + Windows NT whenever any user or group information is modified. If a cached entry has expired, the sequence number is requested from the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information @@ -415,7 +415,7 @@ CLASS="FILENAME" CLASS="COMMAND" >winbindd(8)</B > man page which will provide you - with conguration information and give you sample conguration files. + with configuration information and give you sample configuration files. You may also wish to update the main Samba daemons smbd and nmbd) with a more recent development release, such as the recently announced Samba 2.2 alpha release.</P diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index 938c2dcb2fc..125daccf34c 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -70,7 +70,10 @@ CLASS="FILENAME" of user and group ids specified by the administrator of the Samba system.</P ><P ->The service provided by winbindd is called `winbind' and +>The service provided by <B +CLASS="COMMAND" +>winbindd</B +> is called `winbind' and can be used to resolve user and group information from a Windows NT server. The service can also provide authentication services via an associated PAM module. </P @@ -147,7 +150,7 @@ group: files winbind ><DIV CLASS="REFSECT1" ><A -NAME="AEN52" +NAME="AEN53" ></A ><H2 >OPTIONS</H2 @@ -186,7 +189,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN65" +NAME="AEN66" ></A ><H2 >NAME AND ID RESOLUTION</H2 @@ -217,7 +220,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN71" +NAME="AEN72" ></A ><H2 >CONFIGURATION</H2 @@ -252,7 +255,7 @@ CLASS="COMMAND" DOMAIN\username. In some cases this separator character may cause problems as the '\' character has special meaning in unix shells. In that case you can use the winbind separator - option to specify an alternative sepataror character. Good + option to specify an alternative separator character. Good alternatives may be '/' (although that conflicts with the unix directory separator) or a '+ 'character. The '+' character appears to be the best choice for 100% @@ -276,7 +279,7 @@ CLASS="COMMAND" ><P >The winbind uid parameter specifies the range of user ids that are allocated by the winbindd daemon. - This range of ids should have no existing local or nis users + This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise. </P ><P >Default: <B @@ -296,7 +299,7 @@ CLASS="COMMAND" ><P >The winbind gid parameter specifies the range of group ids that are allocated by the winbindd daemon. - This range of group ids should have no existing local or nis + This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.</P ><P >Default: <B @@ -319,7 +322,7 @@ CLASS="COMMAND" seconds the winbindd daemon will cache user and group information before querying a Windows NT server again. When a item in the cache is older than this time winbindd will ask the domain - controller for the sequence number of the servers account database. + controller for the sequence number of the server's account database. If the sequence number has not changed then the cached item is marked as valid for a further <TT CLASS="PARAMETER" @@ -375,7 +378,10 @@ CLASS="COMMAND" ><EM >Warning:</EM > Turning off user enumeration - may cause some programs to behave oddly. For example, the finger + may cause some programs to behave oddly. For example, the <B +CLASS="COMMAND" +>finger</B +> program relies on having access to the full user list when searching for matching usernames. </P ><P @@ -479,7 +485,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN152" +NAME="AEN154" ></A ><H2 >EXAMPLE SETUP</H2 @@ -577,7 +583,7 @@ CLASS="PARAMETER" >-U</I ></TT > can be any Domain - user that has administrator priviliges on the machine. Next from + user that has administrator privileges on the machine. Next from within <B CLASS="COMMAND" >samedit</B @@ -620,7 +626,10 @@ CLASS="FILENAME" >/lib/libnss_winbind.so.1</TT >.</P ><P ->Finally, setup a smb.conf containing directives like the +>Finally, setup a <TT +CLASS="FILENAME" +>smb.conf</TT +> containing directives like the following: </P ><P ><TABLE @@ -663,7 +672,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN194" +NAME="AEN197" ></A ><H2 >Notes</H2 @@ -723,7 +732,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN210" +NAME="AEN213" ></A ><H2 >Signals</H2 @@ -774,7 +783,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN227" +NAME="AEN230" ></A ><H2 >Files</H2 @@ -848,19 +857,19 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN256" +NAME="AEN259" ></A ><H2 >VERSION</H2 ><P >This man page is correct for version 2.2 of the Samba suite. winbindd is however not available in - stable release of Samba as of yet.</P + the stable release of Samba as of yet.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN259" +NAME="AEN262" ></A ><H2 >SEE ALSO</H2 @@ -888,7 +897,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN266" +NAME="AEN269" ></A ><H2 >AUTHOR</H2 |