diff options
| author | bubulle <bubulle@alioth.debian.org> | 2011-06-16 20:24:37 +0000 |
|---|---|---|
| committer | bubulle <bubulle@alioth.debian.org> | 2011-06-16 20:24:37 +0000 |
| commit | 9c8b6cd6a1bf06ae6efa2d4a8402e481ef5b07b5 (patch) | |
| tree | bef1609198fc014c896e97e2fb16df650ca98155 /docs/htmldocs/Samba3-ByExample/appendix.html | |
| parent | 261cf9325d83b81715ab6a47b4e27bb7e0d367fe (diff) | |
| download | samba-9c8b6cd6a1bf06ae6efa2d4a8402e481ef5b07b5.tar.gz | |
Merge release 3.5.9
git-svn-id: svn://svn.debian.org/svn/pkg-samba/trunk/samba@3825 fc4039ab-9d04-0410-8cac-899223bdd6b0
Diffstat (limited to 'docs/htmldocs/Samba3-ByExample/appendix.html')
| -rw-r--r-- | docs/htmldocs/Samba3-ByExample/appendix.html | 208 |
1 files changed, 104 insertions, 104 deletions
diff --git a/docs/htmldocs/Samba3-ByExample/appendix.html b/docs/htmldocs/Samba3-ByExample/appendix.html index e276164a9f..88e5fc2e48 100644 --- a/docs/htmldocs/Samba3-ByExample/appendix.html +++ b/docs/htmldocs/Samba3-ByExample/appendix.html @@ -1,26 +1,26 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 15. A Collection of Useful Tidbits</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part III. Reference Section"><link rel="prev" href="ch14.html" title="Chapter 14. Samba Support"><link rel="next" href="primer.html" title="Chapter 16. Networking Primer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 15. A Collection of Useful Tidbits</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch14.html">Prev</a> </td><th width="60%" align="center">Part III. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="primer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="appendix"></a>Chapter 15. A Collection of Useful Tidbits</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2621811">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622232">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622592">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622604">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622652">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622792">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622851">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623411">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624406">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2624881">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625028">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625113">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p> - <a class="indexterm" name="id2621228"></a> - <a class="indexterm" name="id2621234"></a> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 15. A Collection of Useful Tidbits</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part III. Reference Section"><link rel="prev" href="ch14.html" title="Chapter 14. Samba Support"><link rel="next" href="primer.html" title="Chapter 16. Networking Primer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 15. A Collection of Useful Tidbits</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch14.html">Prev</a> </td><th width="60%" align="center">Part III. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="primer.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 15. A Collection of Useful Tidbits"><div class="titlepage"><div><div><h2 class="title"><a name="appendix"></a>Chapter 15. A Collection of Useful Tidbits</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="appendix.html#domjoin">Joining a Domain: Windows 200x/XP Professional</a></span></dt><dt><span class="sect1"><a href="appendix.html#id387559">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id387952">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id388254">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id388264">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id388308">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id388408">DNS Root Server Hint File</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#altldapcfg">Alternative LDAP Database Initialization</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id388463">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id388919">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id389839">IDEALX Management Console</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12-SUIDSGID">Effect of Setting File and Directory SUID/SGID Permissions Explained</a></span></dt><dt><span class="sect1"><a href="appendix.html#ch12dblck">Shared Data Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id390270">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id390409">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id390484">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p> + <a class="indexterm" name="id387011"></a> + <a class="indexterm" name="id387018"></a> Information presented here is considered to be either basic or well-known material that is informative yet helpful. Over the years, I have observed an interesting behavior. There is an expectation that the process for joining a Windows client to a Samba-controlled Windows domain may somehow involve steps different from doing so with Windows NT4 or a Windows ADS domain. Be assured that the steps are identical, as shown in the example given below. - </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domjoin"></a>Joining a Domain: Windows 200x/XP Professional</h2></div></div></div><p> - <a class="indexterm" name="id2621264"></a> + </p><div class="sect1" title="Joining a Domain: Windows 200x/XP Professional"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domjoin"></a>Joining a Domain: Windows 200x/XP Professional</h2></div></div></div><p> + <a class="indexterm" name="id387044"></a> Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security. This section steps through the process for making a Windows 200x/XP Professional machine a member of a Domain Security environment. It should be noted that this process is identical when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC. - </p><div class="procedure"><a name="id2621278"></a><p class="title"><b>Procedure 15.1. Steps to Join a Domain</b></p><ol type="1"><li><p> + </p><div class="procedure" title="Procedure 15.1. Steps to Join a Domain"><a name="id387055"></a><p class="title"><b>Procedure 15.1. Steps to Join a Domain</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> Click <span class="guimenu">Start</span>. - </p></li><li><p> + </p></li><li class="step" title="Step 2"><p> Right-click <span class="guimenu">My Computer</span>, and then select <span class="guimenuitem">Properties</span>. - </p></li><li><p> + </p></li><li class="step" title="Step 3"><p> The opening panel is the same one that can be reached by clicking <span class="guimenu">System</span> on the Control Panel. See <a class="link" href="appendix.html#swxpp001" title="Figure 15.1. The General Panel.">“The General Panel.”</a>. </p><div class="figure"><a name="swxpp001"></a><p class="title"><b>Figure 15.1. The General Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp001.png" alt="The General Panel."></div></div></div><p><br class="figure-break"> - </p></li><li><p> + </p></li><li class="step" title="Step 4"><p> Click the <span class="guimenu">Computer Name</span> tab. This panel shows the <span class="guimenuitem">Computer Description</span>, the <span class="guimenuitem">Full computer name</span>, and the <span class="guimenuitem">Workgroup</span> or <span class="guimenuitem">Domain name</span>. @@ -29,40 +29,40 @@ Samba-3. If you wish to change the computer name, or join or leave the domain, click the <span class="guimenu">Change</span> button. See <a class="link" href="appendix.html#swxpp004" title="Figure 15.2. The Computer Name Panel.">“The Computer Name Panel.”</a>. </p><div class="figure"><a name="swxpp004"></a><p class="title"><b>Figure 15.2. The Computer Name Panel.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp004.png" alt="The Computer Name Panel."></div></div></div><p><br class="figure-break"> - </p></li><li><p> + </p></li><li class="step" title="Step 5"><p> Click on <span class="guimenu">Change</span>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP. We join the domain called MIDEARTH. See <a class="link" href="appendix.html#swxpp006" title="Figure 15.3. The Computer Name Changes Panel">“The Computer Name Changes Panel”</a>. </p><div class="figure"><a name="swxpp006"></a><p class="title"><b>Figure 15.3. The Computer Name Changes Panel</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp006.png" alt="The Computer Name Changes Panel"></div></div></div><p><br class="figure-break"> - </p></li><li><p> + </p></li><li class="step" title="Step 6"><p> Enter the name <span class="guimenu">MIDEARTH</span> in the field below the Domain radio button. </p><p> This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <a class="link" href="appendix.html#swxpp007" title="Figure 15.4. The Computer Name Changes Panel Domain MIDEARTH">“The Computer Name Changes Panel Domain MIDEARTH”</a>. </p><div class="figure"><a name="swxpp007"></a><p class="title"><b>Figure 15.4. The Computer Name Changes Panel Domain MIDEARTH</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp007.png" alt="The Computer Name Changes Panel Domain MIDEARTH"></div></div></div><p><br class="figure-break"> - </p></li><li><p> + </p></li><li class="step" title="Step 7"><p> Now click the <span class="guimenu">OK</span> button. A dialog box should appear to allow you to provide the credentials (username and password) of a domain administrative account that has the rights to add machines to the domain. </p><p> - Enter the name “<span class="quote">root</span>” and the root password from your Samba-3 server. See <a class="link" href="appendix.html#swxpp008" title="Figure 15.5. Computer Name Changes User name and Password Panel">“Computer Name Changes User name and Password Panel”</a>. + Enter the name <span class="quote">“<span class="quote">root</span>”</span> and the root password from your Samba-3 server. See <a class="link" href="appendix.html#swxpp008" title="Figure 15.5. Computer Name Changes User name and Password Panel">“Computer Name Changes User name and Password Panel”</a>. </p><div class="figure"><a name="swxpp008"></a><p class="title"><b>Figure 15.5. Computer Name Changes User name and Password Panel</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/wxpp008.png" alt="Computer Name Changes User name and Password Panel"></div></div></div><p><br class="figure-break"> - </p></li><li><p> + </p></li><li class="step" title="Step 8"><p> Click <span class="guimenu">OK</span>. </p><p> - The “<span class="quote">Welcome to the MIDEARTH domain</span>” dialog box should appear. At this point, the machine must be rebooted. + The <span class="quote">“<span class="quote">Welcome to the MIDEARTH domain</span>”</span> dialog box should appear. At this point, the machine must be rebooted. Joining the domain is now complete. </p></li></ol></div><p> - <a class="indexterm" name="id2621696"></a> - <a class="indexterm" name="id2621703"></a> + <a class="indexterm" name="id387460"></a> + <a class="indexterm" name="id387466"></a> The screen capture shown in <a class="link" href="appendix.html#swxpp007" title="Figure 15.4. The Computer Name Changes Panel Domain MIDEARTH">“The Computer Name Changes Panel Domain MIDEARTH”</a> has a button labeled <span class="guimenu">More...</span>. This button opens a panel in which you can set (or change) the Primary DNS suffix of the computer. This is a parameter that mainly affects members of Microsoft Active Directory. Active Directory is heavily oriented around the DNS namespace. </p><p> - <a class="indexterm" name="id2621730"></a> - <a class="indexterm" name="id2621736"></a> + <a class="indexterm" name="id387490"></a> + <a class="indexterm" name="id387497"></a> Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server to find the services (like which machines are domain controllers or which machines have the Netlogon service running). </p><p> - <a class="indexterm" name="id2621755"></a> + <a class="indexterm" name="id387512"></a> The default setting of the Primary DNS suffix is the Active Directory domain name. When you change the Primary DNS suffix, this does not affect domain membership, but it can break network browsing and the ability to resolve your computer name to a valid IP address. @@ -70,12 +70,12 @@ The Primary DNS suffix parameter principally affects MS Windows clients that are members of an Active Directory domain. Where the client is a member of a Samba domain, it is preferable to leave this field blank. </p><p> - <a class="indexterm" name="id2621783"></a> - According to Microsoft documentation, “<span class="quote">If this computer belongs to a group with <code class="constant">Group Policy</code> + <a class="indexterm" name="id387534"></a> + According to Microsoft documentation, <span class="quote">“<span class="quote">If this computer belongs to a group with <code class="constant">Group Policy</code> enabled on <code class="literal">Primary DNS suffice of this computer</code>, the string specified in the Group Policy is used as the primary DNS suffix and you might need to restart your computer to view the correct setting. The local setting is - used only if Group Policy is disabled or unspecified.</span>” - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621811"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id2621818"></a><a class="indexterm" name="id2621826"></a><a class="indexterm" name="id2621834"></a> + used only if Group Policy is disabled or unspecified.</span>”</span> + </p></div><div class="sect1" title="Samba System File Location"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id387559"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id387566"></a><a class="indexterm" name="id387574"></a><a class="indexterm" name="id387581"></a> One of the frustrations expressed by subscribers to the Samba mailing lists revolves around the choice of where the default Samba Team build and installation process locates its Samba files. The location, chosen in the early 1990s, for the default installation is in the <code class="filename">/usr/local/samba</code> directory. This is a perfectly reasonable location, particularly given all the other @@ -83,7 +83,7 @@ </p><p> Several UNIX vendors, and Linux vendors in particular, elected to locate the Samba files in a location other than the Samba Team default. - </p><p><a class="indexterm" name="id2621870"></a><a class="indexterm" name="id2621882"></a><a class="indexterm" name="id2621889"></a><a class="indexterm" name="id2621901"></a><a class="indexterm" name="id2621909"></a><a class="indexterm" name="id2621920"></a><a class="indexterm" name="id2621928"></a><a class="indexterm" name="id2621936"></a><a class="indexterm" name="id2621944"></a><a class="indexterm" name="id2621952"></a><a class="indexterm" name="id2621960"></a><a class="indexterm" name="id2621968"></a><a class="indexterm" name="id2621976"></a><a class="indexterm" name="id2621984"></a><a class="indexterm" name="id2621992"></a><a class="indexterm" name="id2622000"></a> + </p><p><a class="indexterm" name="id387612"></a><a class="indexterm" name="id387624"></a><a class="indexterm" name="id387631"></a><a class="indexterm" name="id387643"></a><a class="indexterm" name="id387650"></a><a class="indexterm" name="id387662"></a><a class="indexterm" name="id387670"></a><a class="indexterm" name="id387677"></a><a class="indexterm" name="id387685"></a><a class="indexterm" name="id387693"></a><a class="indexterm" name="id387701"></a><a class="indexterm" name="id387709"></a><a class="indexterm" name="id387717"></a><a class="indexterm" name="id387725"></a><a class="indexterm" name="id387732"></a><a class="indexterm" name="id387740"></a> Linux vendors, working in conjunction with the Free Standards Group (FSG), Linux Standards Base (LSB), and File Hierarchy System (FHS), have elected to locate the configuration files under the <code class="filename">/etc/samba</code> directory, common binary files (those used by users) in the <code class="filename">/usr/bin</code> directory, and the administrative files (daemons) in the @@ -92,13 +92,13 @@ <code class="filename">/usr/share/swat</code>. There are additional support files for <code class="literal">smbd</code> in the <code class="filename">/usr/lib/samba</code> directory tree. The files located there include the dynamically loadable modules for the passdb backend as well as for the VFS modules. - </p><p><a class="indexterm" name="id2622069"></a><a class="indexterm" name="id2622077"></a><a class="indexterm" name="id2622085"></a> + </p><p><a class="indexterm" name="id387804"></a><a class="indexterm" name="id387812"></a><a class="indexterm" name="id387820"></a> Samba creates runtime control files and generates log files. The runtime control files (tdb and dat files) are stored in the <code class="filename">/var/lib/samba</code> directory. Log files are created in <code class="filename">/var/log/samba.</code> </p><p> When Samba is built and installed using the default Samba Team process, all files are located under the <code class="filename">/usr/local/samba</code> directory tree. This makes it simple to find the files that Samba owns. - </p><p><a class="indexterm" name="id2622123"></a> + </p><p><a class="indexterm" name="id387854"></a> One way to find the Samba files that are installed on your UNIX/Linux system is to search for the location of all files called <code class="literal">smbd</code>. Here is an example: </p><pre class="screen"> @@ -131,7 +131,7 @@ Version 3.0.20-SUSE </p><p> Many people have been caught by installation of Samba using the default Samba Team process when it was already installed by the platform vendor's method. If your platform uses RPM format packages, you can check to see if Samba is installed by - executing:<a class="indexterm" name="id2622196"></a> + executing:<a class="indexterm" name="id387919"></a> </p><pre class="screen"> <code class="prompt">root# </code> rpm -qa | grep samba samba3-pdb-3.0.20-1 @@ -143,9 +143,9 @@ samba3-utils-3.0.20-1 samba3-doc-3.0.20-1 samba3-client-3.0.20-1 samba3-cifsmount-3.0.20-1 - </pre><p><a class="indexterm" name="id2622219"></a> + </pre><p><a class="indexterm" name="id387940"></a> The package names, of course, vary according to how the vendor, or the binary package builder, prepared them. - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622232"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id2622239"></a> + </p></div><div class="sect1" title="Starting Samba"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id387952"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id387958"></a> Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services. An example of a service is the Apache Web server for which the daemon is called <code class="literal">httpd</code>. In the case of Samba, there are three daemons, two of which are needed as a minimum. @@ -186,19 +186,19 @@ if [ $1 == 'restart' ]; then fi exit 0 </pre></div></div><br class="example-break"><div class="variablelist"><dl><dt><span class="term">nmbd</span></dt><dd><p> - <a class="indexterm" name="id2622312"></a> - <a class="indexterm" name="id2622319"></a> + <a class="indexterm" name="id388017"></a> + <a class="indexterm" name="id388024"></a> This daemon handles all name registration and resolution requests. It is the primary vehicle involved in network browsing. It handles all UDP-based protocols. The <code class="literal">nmbd</code> daemon should be the first command started as part of the Samba startup process. </p></dd><dt><span class="term">smbd</span></dt><dd><p> - <a class="indexterm" name="id2622349"></a> - <a class="indexterm" name="id2622355"></a> + <a class="indexterm" name="id388051"></a> + <a class="indexterm" name="id388058"></a> This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also manages local authentication. It should be started immediately following the startup of <code class="literal">nmbd</code>. </p></dd><dt><span class="term">winbindd</span></dt><dd><p> - <a class="indexterm" name="id2622384"></a> - <a class="indexterm" name="id2622391"></a> + <a class="indexterm" name="id388085"></a> + <a class="indexterm" name="id388092"></a> This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when Samba has trust relationships with another domain. The <code class="literal">winbindd</code> daemon will check the <code class="filename">smb.conf</code> file for the presence of the <em class="parameter"><code>idmap uid</code></em> and <em class="parameter"><code>idmap gid</code></em> @@ -252,22 +252,22 @@ case "$1" in echo "Usage: smb {start|stop|restart|status}" exit 1 esac -</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2622513"></a> +</pre></div></div><br class="example-break"><p><a class="indexterm" name="id388184"></a> SUSE Linux implements individual control over each Samba daemon. A Samba control script that can be conveniently executed from the command line is shown in <a class="link" href="appendix.html#ch12SL" title="Example 15.1. A Useful Samba Control Script for SUSE Linux">“A Useful Samba Control Script for SUSE Linux”</a>. This can be located in the directory <code class="filename">/sbin</code> in a file called <code class="filename">samba</code>. This type of control script should be owned by user root and group root, and set so that only root can execute it. - </p><p><a class="indexterm" name="id2622549"></a> + </p><p><a class="indexterm" name="id388216"></a> A sample startup script for a Red Hat Linux system is shown in <a class="link" href="appendix.html#ch12RHscript" title="Example 15.2. A Sample Samba Control Script for Red Hat Linux">“A Sample Samba Control Script for Red Hat Linux”</a>. This file could be located in the directory <code class="filename">/etc/rc.d</code> and can be called <code class="filename">samba</code>. A similar startup script is required to control <code class="literal">winbind</code>. If you want to find more information regarding startup scripts please refer to the packaging section of the Samba source code distribution tarball. The packaging files for each platform include a startup control file. - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622592"></a>DNS Configuration Files</h2></div></div></div><p> + </p></div><div class="sect1" title="DNS Configuration Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id388254"></a>DNS Configuration Files</h2></div></div></div><p> The following files are common to all DNS server configurations. Rather than repeat them multiple times, they are presented here for general reference. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622604"></a>The Forward Zone File for the Loopback Adaptor</h3></div></div></div><p> + </p><div class="sect2" title="The Forward Zone File for the Loopback Adaptor"><div class="titlepage"><div><div><h3 class="title"><a name="id388264"></a>The Forward Zone File for the Loopback Adaptor</h3></div></div></div><p> The forward zone file for the loopback address never changes. An example file is shown in <a class="link" href="appendix.html#loopback" title="Example 15.3. DNS Localhost Forward Zone File: /var/lib/named/localhost.zone">“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”</a>. All traffic destined for an IP address that is hosted on a physical interface on the machine itself is routed to the loopback adaptor. This is @@ -284,7 +284,7 @@ $TTL 1W IN NS @ IN A 127.0.0.1 -</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622652"></a>The Reverse Zone File for the Loopback Adaptor</h3></div></div></div><p> +</pre></div></div><br class="example-break"></div><div class="sect2" title="The Reverse Zone File for the Loopback Adaptor"><div class="titlepage"><div><div><h3 class="title"><a name="id388308"></a>The Reverse Zone File for the Loopback Adaptor</h3></div></div></div><p> The reverse zone file for the loopback address as shown in <a class="link" href="appendix.html#dnsloopy" title="Example 15.4. DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone">“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”</a> is necessary so that references to the address <code class="constant">127.0.0.1</code> can be resolved to the correct name of the interface. @@ -344,21 +344,21 @@ L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12 . 3600000 NS M.ROOT-SERVERS.NET. M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33 ; End of File -</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622792"></a>DNS Root Server Hint File</h3></div></div></div><p> +</pre></div></div><br class="example-break"></div><div class="sect2" title="DNS Root Server Hint File"><div class="titlepage"><div><div><h3 class="title"><a name="id388408"></a>DNS Root Server Hint File</h3></div></div></div><p> The content of the root hints file as shown in <a class="link" href="appendix.html#roothint" title="Example 15.5. DNS Root Name Server Hint File: /var/lib/named/root.hint">“DNS Root Name Server Hint File: /var/lib/named/root.hint”</a> changes slowly over time. Periodically this file should be updated from the source shown. Because of its size, this file is located at the end of this chapter. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altldapcfg"></a>Alternative LDAP Database Initialization</h2></div></div></div><p><a class="indexterm" name="id2622823"></a><a class="indexterm" name="id2622834"></a> + </p></div></div><div class="sect1" title="Alternative LDAP Database Initialization"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="altldapcfg"></a>Alternative LDAP Database Initialization</h2></div></div></div><p><a class="indexterm" name="id388437"></a><a class="indexterm" name="id388448"></a> The following procedure may be used as an alternative means of configuring the initial LDAP database. Many administrators prefer to have greater control over how system files get configured. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622851"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id2622858"></a><a class="indexterm" name="id2622866"></a><a class="indexterm" name="id2622878"></a> + </p><div class="sect2" title="Initialization of the LDAP Database"><div class="titlepage"><div><div><h3 class="title"><a name="id388463"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id388470"></a><a class="indexterm" name="id388478"></a><a class="indexterm" name="id388489"></a> The first step to get the LDAP server ready for action is to create the LDIF file from which the LDAP database will be preloaded. This is necessary to create the containers into which the user, group, and other accounts are written. It is also necessary to preload the well-known Windows NT Domain Groups, as they must have the correct SID so that they can be recognized as special NT Groups by the MS Windows clients. - </p><div class="procedure"><a name="ldapinit"></a><p class="title"><b>Procedure 15.2. LDAP Directory Pre-Load Steps</b></p><ol type="1"><li><p> + </p><div class="procedure" title="Procedure 15.2. LDAP Directory Pre-Load Steps"><a name="ldapinit"></a><p class="title"><b>Procedure 15.2. LDAP Directory Pre-Load Steps</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> Create a directory in which to store the files you use to generate the LDAP LDIF file for your system. Execute the following: </p><pre class="screen"> @@ -366,16 +366,16 @@ M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33 <code class="prompt">root# </code> chown root:root /etc/openldap/SambaInit <code class="prompt">root# </code> chmod 700 /etc/openldap/SambaInit </pre><p> - </p></li><li><p> + </p></li><li class="step" title="Step 2"><p> Install the files shown in <a class="link" href="appendix.html#sbehap-ldapreconfa" title="Example 15.6. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A">“LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A”</a>, <a class="link" href="appendix.html#sbehap-ldapreconfb" title="Example 15.7. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B">“LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B”</a>, and <a class="link" href="appendix.html#sbehap-ldapreconfc" title="Example 15.8. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C">“LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C”</a> into the directory <code class="filename">/etc/openldap/SambaInit/SMBLDAP-ldif-preconfig.sh.</code> These three files are, respectively, parts A, B, and C of the <code class="filename">SMBLDAP-ldif-preconfig.sh</code> file. - </p></li><li><p> + </p></li><li class="step" title="Step 3"><p> Install the files shown in <a class="link" href="appendix.html#sbehap-ldifpata" title="Example 15.9. LDIF Pattern File Used to Pre-configure LDAP Part A">“LDIF Pattern File Used to Pre-configure LDAP Part A”</a> and <a class="link" href="appendix.html#sbehap-ldifpatb" title="Example 15.10. LDIF Pattern File Used to Pre-configure LDAP Part B">“LDIF Pattern File Used to Pre-configure LDAP Part B”</a> into the directory <code class="filename">/etc/openldap/SambaInit/.</code> These two files are parts A and B, respectively, of the <code class="filename">init-ldif.pat</code> file. - </p></li><li><p> + </p></li><li class="step" title="Step 4"><p> Change to the <code class="filename">/etc/openldap/SambaInit</code> directory. Execute the following: </p><pre class="screen"> <code class="prompt">root# </code> sh SMBLDAP-ldif-preconfig.sh @@ -415,7 +415,7 @@ Enter the top level org name or press Enter to continue: <code class="prompt">root# </code> </pre><p> This creates a file called <code class="filename">MEGANET2.ldif</code>. - </p></li><li><p> + </p></li><li class="step" title="Step 5"><p> It is now time to preload the LDAP database with the following command: </p><pre class="screen"> @@ -466,14 +466,14 @@ createTimestamp: 20031217055747Z modifyTimestamp: 20031217055747Z entryCSN: 2003121705:57:47Z#0x000a#0#0000 </pre><p> - </p></li><li><p> + </p></li><li class="step" title="Step 6"><p> Your LDAP database is ready for testing. You can now start the LDAP server using the system tool for your Linux operating system. For SUSE Linux, you can do this as follows: </p><pre class="screen"> <code class="prompt">root# </code> rcldap start </pre><p> - </p></li><li><p> + </p></li><li class="step" title="Step 7"><p> It is now a good idea to validate that the LDAP server is running correctly. Execute the following: </p><pre class="screen"> @@ -705,14 +705,14 @@ sambaSID: DOMSID-513 sambaGroupType: 2 displayName: Domain Users description: Domain Users -</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2623411"></a>The LDAP Account Manager</h2></div></div></div><p> -<a class="indexterm" name="id2623419"></a> -<a class="indexterm" name="id2623426"></a> -<a class="indexterm" name="id2623435"></a> -<a class="indexterm" name="id2623442"></a> -<a class="indexterm" name="id2623448"></a> -<a class="indexterm" name="id2623455"></a> -<a class="indexterm" name="id2623462"></a> +</pre></div></div><br class="example-break"></div><div class="sect1" title="The LDAP Account Manager"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id388919"></a>The LDAP Account Manager</h2></div></div></div><p> +<a class="indexterm" name="id388927"></a> +<a class="indexterm" name="id388934"></a> +<a class="indexterm" name="id388943"></a> +<a class="indexterm" name="id388949"></a> +<a class="indexterm" name="id388956"></a> +<a class="indexterm" name="id388963"></a> +<a class="indexterm" name="id388970"></a> The LDAP Account Manager (LAM) is an application suite that has been written in PHP. LAM can be used with any Web server that has PHP4 support. It connects to the LDAP server either using unencrypted connections or via SSL/TLS. LAM can be used to manage @@ -724,29 +724,29 @@ home page and from its mirror sites. LAM has been released under the GNU GPL ver The current version of LAM is 0.4.9. Release of version 0.5 is expected in the third quarter of 2005. </p><p> -<a class="indexterm" name="id2623493"></a> -<a class="indexterm" name="id2623500"></a> -<a class="indexterm" name="id2623507"></a> +<a class="indexterm" name="id388996"></a> +<a class="indexterm" name="id389003"></a> +<a class="indexterm" name="id389010"></a> Requirements: -</p><div class="itemizedlist"><ul type="disc"><li><p>A web server that will work with PHP4.</p></li><li><p>PHP4 (available from the <a class="ulink" href="http://www.php.net/" target="_top">PHP</a> home page.)</p></li><li><p>OpenLDAP 2.0 or later.</p></li><li><p>A Web browser that supports CSS.</p></li><li><p>Perl.</p></li><li><p>The gettext package.</p></li><li><p>mcrypt + mhash (optional).</p></li><li><p>It is also a good idea to install SSL support.</p></li></ul></div><p> +</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A web server that will work with PHP4.</p></li><li class="listitem"><p>PHP4 (available from the <a class="ulink" href="http://www.php.net/" target="_top">PHP</a> home page.)</p></li><li class="listitem"><p>OpenLDAP 2.0 or later.</p></li><li class="listitem"><p>A Web browser that supports CSS.</p></li><li class="listitem"><p>Perl.</p></li><li class="listitem"><p>The gettext package.</p></li><li class="listitem"><p>mcrypt + mhash (optional).</p></li><li class="listitem"><p>It is also a good idea to install SSL support.</p></li></ul></div><p> LAM is a useful tool that provides a simple Web-based device that can be used to manage the contents of the LDAP directory to: -<a class="indexterm" name="id2623568"></a> -<a class="indexterm" name="id2623575"></a> -<a class="indexterm" name="id2623582"></a> -</p><div class="itemizedlist"><ul type="disc"><li><p>Display user/group/host and Domain entries.</p></li><li><p>Manage entries (Add/Delete/Edit).</p></li><li><p>Filter and sort entries.</p></li><li><p>Store and use multiple operating profiles.</p></li><li><p>Edit organizational units (OUs).</p></li><li><p>Upload accounts from a file.</p></li><li><p>Is compatible with Samba-2.2.x and Samba-3.</p></li></ul></div><p> +<a class="indexterm" name="id389067"></a> +<a class="indexterm" name="id389074"></a> +<a class="indexterm" name="id389081"></a> +</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Display user/group/host and Domain entries.</p></li><li class="listitem"><p>Manage entries (Add/Delete/Edit).</p></li><li class="listitem"><p>Filter and sort entries.</p></li><li class="listitem"><p>Store and use multiple operating profiles.</p></li><li class="listitem"><p>Edit organizational units (OUs).</p></li><li class="listitem"><p>Upload accounts from a file.</p></li><li class="listitem"><p>Is compatible with Samba-2.2.x and Samba-3.</p></li></ul></div><p> When correctly configured, LAM allows convenient management of UNIX (Posix) and Samba user, group, and windows domain member machine accounts. </p><p> -<a class="indexterm" name="id2623636"></a> -<a class="indexterm" name="id2623643"></a> -<a class="indexterm" name="id2623650"></a> -<a class="indexterm" name="id2623656"></a> -The default password is “<span class="quote">lam.</span>” It is highly recommended that you use only +<a class="indexterm" name="id389132"></a> +<a class="indexterm" name="id389139"></a> +<a class="indexterm" name="id389145"></a> +<a class="indexterm" name="id389152"></a> +The default password is <span class="quote">“<span class="quote">lam.</span>”</span> It is highly recommended that you use only an SSL connection to your Web server for all remote operations involving LAM. If you want secure connections, you must configure your Apache Web server to permit connections to LAM using only SSL. -</p><div class="procedure"><a name="sbehap-laminst"></a><p class="title"><b>Procedure 15.3. Apache Configuration Steps for LAM</b></p><ol type="1"><li><p> +</p><div class="procedure" title="Procedure 15.3. Apache Configuration Steps for LAM"><a name="sbehap-laminst"></a><p class="title"><b>Procedure 15.3. Apache Configuration Steps for LAM</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> Extract the LAM package by untarring it as shown here: </p><pre class="screen"> <code class="prompt">root# </code> tar xzf ldap-account-manager_0.4.9.tar.gz @@ -755,12 +755,12 @@ to LAM using only SSL. </p><pre class="screen"> <code class="prompt">root# </code> dpkg -i ldap-account-manager_0.4.9.all.deb </pre><p> - </p></li><li><p> + </p></li><li class="step" title="Step 2"><p> Copy the extracted files to the document root directory of your Web server. For example, on SUSE Linux Enterprise Server 9, copy to the <code class="filename">/srv/www/htdocs</code> directory. - </p></li><li><p> - <a class="indexterm" name="id2623736"></a> + </p></li><li class="step" title="Step 3"><p> + <a class="indexterm" name="id389226"></a> Set file permissions using the following commands: </p><pre class="screen"> <code class="prompt">root# </code> chown -R wwwrun:www /srv/www/htdocs/lam @@ -769,8 +769,8 @@ to LAM using only SSL. <code class="prompt">root# </code> chmod 755 /srv/www/htdocs/lam/config <code class="prompt">root# </code> chmod 755 /srv/www/htdocs/lam/lib/*pl </pre><p> - </p></li><li><p> - <a class="indexterm" name="id2623789"></a> + </p></li><li class="step" title="Step 4"><p> + <a class="indexterm" name="id389276"></a> Using your favorite editor create the following <code class="filename">config.cfg</code> LAM configuration file: </p><pre class="screen"> @@ -778,13 +778,13 @@ to LAM using only SSL. <code class="prompt">root# </code> cp config.cfg_sample config.cfg <code class="prompt">root# </code> vi config.cfg </pre><p> - <a class="indexterm" name="id2623830"></a> - <a class="indexterm" name="id2623839"></a> + <a class="indexterm" name="id389315"></a> + <a class="indexterm" name="id389324"></a> An example file is shown in <a class="link" href="appendix.html#lamcfg" title="Example 15.11. Example LAM Configuration File config.cfg">“Example LAM Configuration File config.cfg”</a>. This is the minimum configuration that must be completed. The LAM profile file can be created using a convenient wizard that is part of the LAM configuration suite. - </p></li><li><p> + </p></li><li class="step" title="Step 5"><p> Start your Web server then, using your Web browser, connect to <a class="ulink" href="http://localhost/lam" target="_top">LAM</a> URL. Click on the the <em class="parameter"><code>Configuration Login</code></em> link then click on the @@ -794,7 +794,7 @@ to LAM using only SSL. <code class="filename">lam.conf</code> then, using your favorite editor, change the settings to match local site needs. </p></li></ol></div><p> - <a class="indexterm" name="id2623898"></a> + <a class="indexterm" name="id389379"></a> An example of a working file is shown here in <a class="link" href="appendix.html#lamconf" title="Example 15.12. LAM Profile Control File lam.conf">“LAM Profile Control File lam.conf”</a>. This file has been stripped of comments to keep the size small. The comments and help information provided in the profile file that the wizard creates @@ -802,12 +802,12 @@ to LAM using only SSL. Your configuration file obviously reflects the configuration options that are preferred at your site. </p><p> - <a class="indexterm" name="id2623921"></a> + <a class="indexterm" name="id389399"></a> It is important that your LDAP server is running at the time that LAM is being configured. This permits you to validate correct operation. An example of the LAM login screen is provided in <a class="link" href="appendix.html#lam-login" title="Figure 15.6. The LDAP Account Manager Login Screen">“The LDAP Account Manager Login Screen”</a>. </p><div class="figure"><a name="lam-login"></a><p class="title"><b>Figure 15.6. The LDAP Account Manager Login Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-login.png" width="270" alt="The LDAP Account Manager Login Screen"></div></div></div><br class="figure-break"><p> - <a class="indexterm" name="id2623984"></a> + <a class="indexterm" name="id389458"></a> The LAM configuration editor has a number of options that must be managed correctly. An example of use of the LAM configuration editor is shown in <a class="link" href="appendix.html#lam-config" title="Figure 15.7. The LDAP Account Manager Configuration Screen">“The LDAP Account Manager Configuration Screen”</a>. It is important that you correctly set the minimum and maximum UID/GID values that are @@ -817,13 +817,13 @@ to LAM using only SSL. the initial settings to be made. Do not forget to reset these to sensible values before using LAM to add additional users and groups. </p><div class="figure"><a name="lam-config"></a><p class="title"><b>Figure 15.7. The LDAP Account Manager Configuration Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-config.png" width="270" alt="The LDAP Account Manager Configuration Screen"></div></div></div><br class="figure-break"><p> - <a class="indexterm" name="id2624056"></a> + <a class="indexterm" name="id389523"></a> LAM has some nice, but unusual features. For example, one unexpected feature in most application screens permits the generation of a PDF file that lists configuration information. This is a well thought out facility. This option has been edited out of the following screen shots to conserve space. </p><p> - <a class="indexterm" name="id2624071"></a> + <a class="indexterm" name="id389536"></a> When you log onto LAM the opening screen drops you right into the user manager as shown in <a class="link" href="appendix.html#lam-user" title="Figure 15.8. The LDAP Account Manager User Edit Screen">“The LDAP Account Manager User Edit Screen”</a>. This is a logical action as it permits the most-needed facility to be used immediately. The editing of an existing user, as with the addition of a new user, @@ -837,7 +837,7 @@ to LAM using only SSL. shows a sub-screen from the group editor that permits users to be assigned secondary group memberships. </p><div class="figure"><a name="lam-group"></a><p class="title"><b>Figure 15.9. The LDAP Account Manager Group Edit Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-groups.png" width="270" alt="The LDAP Account Manager Group Edit Screen"></div></div></div><br class="figure-break"><div class="figure"><a name="lam-group-mem"></a><p class="title"><b>Figure 15.10. The LDAP Account Manager Group Membership Edit Screen</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/lam-group-members.png" width="270" alt="The LDAP Account Manager Group Membership Edit Screen"></div></div></div><br class="figure-break"><p> - <a class="indexterm" name="id2624251"></a><a class="indexterm" name="id2624256"></a> + <a class="indexterm" name="id389704"></a><a class="indexterm" name="id389710"></a> The final screen presented here is one that you should not normally need to use. Host accounts will be automatically managed using the smbldap-tools scripts. This means that the screen <a class="link" href="appendix.html#lam-host" title="Figure 15.11. The LDAP Account Manager Host Edit Screen">“The LDAP Account Manager Host Edit Screen”</a> will, in most cases, not be used. @@ -883,7 +883,7 @@ scriptServer: samba3: yes cachetimeout: 5 pwdhash: SSHA -</pre></div></div><br class="example-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2624406"></a>IDEALX Management Console</h2></div></div></div><p> +</pre></div></div><br class="example-break"></div><div class="sect1" title="IDEALX Management Console"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id389839"></a>IDEALX Management Console</h2></div></div></div><p> IMC (the IDEALX Mamagement Console) is a tool that can be used as the basis for a comprehensive web-based management interface for UNIX and Linux systems. </p><p> @@ -897,7 +897,7 @@ pwdhash: SSHA </p><p> For further information regarding IMC refer to the web <a class="ulink" href="http://imc.sourceforge.net/" target="_top">site.</a> Prebuilt RPM packages are also <a class="ulink" href="http://imc.sourceforge.net/download.html" target="_top">available.</a> - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12-SUIDSGID"></a>Effect of Setting File and Directory SUID/SGID Permissions Explained</h2></div></div></div><a class="indexterm" name="id2624512"></a><a class="indexterm" name="id2624519"></a><p> + </p></div><div class="sect1" title="Effect of Setting File and Directory SUID/SGID Permissions Explained"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12-SUIDSGID"></a>Effect of Setting File and Directory SUID/SGID Permissions Explained</h2></div></div></div><a class="indexterm" name="id389935"></a><a class="indexterm" name="id389942"></a><p> The setting of the SUID/SGID bits on the file or directory permissions flag has particular consequences. If the file is executable and the SUID bit is set, it executes with the privilege of (with the UID of) the owner of the file. For example, if you are logged onto a system as @@ -967,34 +967,34 @@ drwx------ 2 root root 48 Jan 26 2002 lost+found total 1 drw-rw-r-- 2 bobj Domain Users 12346 Dec 18 18:11 maryvfile.txt </pre><p> - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12dblck"></a>Shared Data Integrity</h2></div></div></div><p><a class="indexterm" name="id2624750"></a><a class="indexterm" name="id2624757"></a> + </p></div><div class="sect1" title="Shared Data Integrity"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ch12dblck"></a>Shared Data Integrity</h2></div></div></div><p><a class="indexterm" name="id390147"></a><a class="indexterm" name="id390155"></a> The integrity of shared data is often viewed as a particularly emotional issue, especially where there are concurrent problems with multiuser data access. Contrary to the assertions of some who have experienced problems in either area, the cause has nothing to do with the phases of the moons of Jupiter. </p><p> The solution to concurrent multiuser data access problems must consider three separate areas - from which the problem may stem:<a class="indexterm" name="id2624781"></a><a class="indexterm" name="id2624792"></a><a class="indexterm" name="id2624803"></a> - </p><div class="itemizedlist"><ul type="disc"><li><p>application-level locking controls</p></li><li><p>client-side locking controls</p></li><li><p>server-side locking controls</p></li></ul></div><p><a class="indexterm" name="id2624836"></a><a class="indexterm" name="id2624844"></a> + from which the problem may stem:<a class="indexterm" name="id390175"></a><a class="indexterm" name="id390186"></a><a class="indexterm" name="id390197"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>application-level locking controls</p></li><li class="listitem"><p>client-side locking controls</p></li><li class="listitem"><p>server-side locking controls</p></li></ul></div><p><a class="indexterm" name="id390229"></a><a class="indexterm" name="id390237"></a> Many database applications use some form of application-level access control. An example of one well-known application that uses application-level locking is Microsoft Access. Detailed guidance is provided here because this is the most common application for which problems have been reported. - </p><p><a class="indexterm" name="id2624860"></a><a class="indexterm" name="id2624868"></a> + </p><p><a class="indexterm" name="id390251"></a><a class="indexterm" name="id390259"></a> Common applications that are affected by client- and server-side locking controls include MS Excel and Act!. Important locking guidance is provided here. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2624881"></a>Microsoft Access</h3></div></div></div><p> + </p><div class="sect2" title="Microsoft Access"><div class="titlepage"><div><div><h3 class="title"><a name="id390270"></a>Microsoft Access</h3></div></div></div><p> The best advice that can be given is to carefully read the Microsoft knowledgebase articles that cover this area. Examples of relevant documents include: - </p><div class="itemizedlist"><ul type="disc"><li><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</p></li><li><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</p></li></ul></div><p><a class="indexterm" name="id2624908"></a><a class="indexterm" name="id2624919"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</p></li><li class="listitem"><p>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</p></li></ul></div><p><a class="indexterm" name="id390294"></a><a class="indexterm" name="id390306"></a> Make sure that your MS Access database file is configured for multiuser access (not set for exclusive open). Open MS Access on each client workstation, then set the following: <span class="guimenu">(Menu bar) Tools</span>+<span class="guimenu">Options</span>+<span class="guimenu">[tab] General</span>. Set network path to Default database folder: <code class="filename">\\server\share\folder</code>. </p><p> You can configure MS Access file sharing behavior as follows: click <span class="guimenu">[tab] Advanced</span>. - Set:<a class="indexterm" name="id2624970"></a> - </p><div class="itemizedlist"><ul type="disc"><li><p>Default open mode: Shared</p></li><li><p>Default Record Locking: Edited Record</p></li><li><p>Open databases using record_level locking</p></li></ul></div><p><a class="indexterm" name="id2625000"></a> + Set:<a class="indexterm" name="id390353"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Default open mode: Shared</p></li><li class="listitem"><p>Default Record Locking: Edited Record</p></li><li class="listitem"><p>Open databases using record_level locking</p></li></ul></div><p><a class="indexterm" name="id390382"></a> You must now commit the changes so that they will take effect. To do so, click <span class="guimenu">Apply</span><span class="guimenu">Ok</span>. At this point, you should exit MS Access, restart it, and then validate that these settings have not changed. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625028"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id2625035"></a><a class="indexterm" name="id2625043"></a> + </p></div><div class="sect2" title="Act! Database Sharing"><div class="titlepage"><div><div><h3 class="title"><a name="id390409"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id390415"></a><a class="indexterm" name="id390423"></a> Where the server sharing the ACT! database(s) is running Samba,or Windows NT, 200x, or XP, you must disable opportunistic locking on the server and all workstations. Failure to do so results in data corruption. This information is available from the Act! Web site @@ -1002,7 +1002,7 @@ drw-rw-r-- 2 bobj Domain Users 12346 Dec 18 18:11 maryvfile.txt <a class="ulink" href="http://itdomino.saleslogix.com/act.nsf/docid/1998223162925" target="_top">1998223162925</a> as well as from article <a class="ulink" href="http://itdomino.saleslogix.com/act.nsf/docid/200110485036" target="_top">200110485036</a>. - </p><p><a class="indexterm" name="id2625073"></a><a class="indexterm" name="id2625081"></a> + </p><p><a class="indexterm" name="id390449"></a><a class="indexterm" name="id390457"></a> These documents clearly state that opportunistic locking must be disabled on both the server (Samba in the case we are interested in here), as well as on every workstation from which the centrally shared Act! database will be accessed. Act! provides @@ -1010,18 +1010,18 @@ drw-rw-r-- 2 bobj Domain Users 12346 Dec 18 18:11 maryvfile.txt registry settings that may otherwise interfere with the operation of Act! Registered Act! users may download this utility from the Act! Web <a class="ulink" href="http://www.act.com/support/updates/index.cfm" target="_top">site.</a> - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625113"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id2625120"></a> + </p></div><div class="sect2" title="Opportunistic Locking Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id390484"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id390491"></a> Third-party Windows applications may not be compatible with the use of opportunistic file - and record locking. For applications that are known not to be compatible,<sup>[<a name="id2625132" href="#ftn.id2625132" class="footnote">14</a>]</sup> oplock + and record locking. For applications that are known not to be compatible,<sup>[<a name="id390501" href="#ftn.id390501" class="footnote">14</a>]</sup> oplock support may need to be disabled both on the Samba server and on the Windows workstations. - </p><p><a class="indexterm" name="id2625147"></a><a class="indexterm" name="id2625155"></a><a class="indexterm" name="id2625163"></a> + </p><p><a class="indexterm" name="id390512"></a><a class="indexterm" name="id390520"></a><a class="indexterm" name="id390528"></a> Oplocks enable a Windows client to cache parts of a file that are being edited. Another windows client may then request to open the file with the ability to write to it. The server will then ask the original workstation that had the file open with a write lock to release its lock. Before doing so, that workstation must flush the file from cache memory to the disk or network drive. - </p><p><a class="indexterm" name="id2625184"></a> + </p><p><a class="indexterm" name="id390546"></a> Disabling of Oplocks usage may require server and client changes. Oplocks may be disabled by file, by file pattern, on the share, or on the Samba server. @@ -1057,7 +1057,7 @@ REGEDIT4 </p><p> Comprehensive coverage of file and record-locking controls is provided in TOSHARG2, Chapter 13. The information in that chapter was obtained from a wide variety of sources. - </p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2625132" href="#id2625132" class="para">14</a>] </sup>Refer to + </p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id390501" href="#id390501" class="para">14</a>] </sup>Refer to the application manufacturer's installation guidelines and knowledge base for specific information regarding compatibility. It is often safe to assume that if the software manufacturer does not specifically mention incompatibilities with opportunistic file |