1
<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#id2621955">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622376">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2622715">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2622727">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622776">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2622916">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#id2622975">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2623561">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2624558">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#id2625032">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625180">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2625264">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p>
2
<a class="indexterm" name="id2621376"></a>
3
<a class="indexterm" name="id2621382"></a>
1
<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#id2628013">Samba System File Location</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628434">Starting Samba</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2628774">DNS Configuration Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="appendix.html#id2628786">The Forward Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628834">The Reverse Zone File for the Loopback Adaptor</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2628974">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#id2629033">Initialization of the LDAP Database</a></span></dt></dl></dd><dt><span class="sect1"><a href="appendix.html#id2629619">The LDAP Account Manager</a></span></dt><dt><span class="sect1"><a href="appendix.html#id2630616">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#id2631091">Microsoft Access</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631238">Act! Database Sharing</a></span></dt><dt><span class="sect2"><a href="appendix.html#id2631322">Opportunistic Locking Controls</a></span></dt></dl></dd></dl></div><p>
2
<a class="indexterm" name="id2627434"></a>
3
<a class="indexterm" name="id2627441"></a>
4
4
Information presented here is considered to be either basic or well-known material that is informative
5
5
yet helpful. Over the years, I have observed an interesting behavior. There is an expectation that
6
6
the process for joining a Windows client to a Samba-controlled Windows domain may somehow involve steps
7
7
different from doing so with Windows NT4 or a Windows ADS domain. Be assured that the steps are identical,
8
8
as shown in the example given below.
9
</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>
10
<a class="indexterm" name="id2621412"></a>
9
</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>
10
<a class="indexterm" name="id2627471"></a>
11
11
Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security.
12
12
This section steps through the process for making a Windows 200x/XP Professional machine a
13
13
member of a Domain Security environment. It should be noted that this process is identical
14
14
when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
15
</p><div class="procedure"><a name="id2621426"></a><p class="title"><b>Procedure�15.1.�Steps to Join a Domain</b></p><ol type="1"><li><p>
15
</p><div class="procedure" title="Procedure�15.1.�Steps to Join a Domain"><a name="id2627485"></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>
16
16
Click <span class="guimenu">Start</span>.
17
</p></li><li class="step" title="Step 2"><p>
18
18
Right-click <span class="guimenu">My Computer</span>, and then select <span class="guimenuitem">Properties</span>.
19
</p></li><li class="step" title="Step 3"><p>
20
20
The opening panel is the same one that can be reached by clicking <span class="guimenu">System</span> on the Control Panel.
21
21
See <a class="link" href="appendix.html#swxpp001" title="Figure�15.1.�The General Panel.">“The General Panel.”</a>.
22
22
</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">
23
</p></li><li class="step" title="Step 4"><p>
24
24
Click the <span class="guimenu">Computer Name</span> tab.
25
25
This panel shows the <span class="guimenuitem">Computer Description</span>, the <span class="guimenuitem">Full computer name</span>,
26
26
and the <span class="guimenuitem">Workgroup</span> or <span class="guimenuitem">Domain name</span>.
29
29
Samba-3. If you wish to change the computer name, or join or leave the domain, click the <span class="guimenu">Change</span> button.
30
30
See <a class="link" href="appendix.html#swxpp004" title="Figure�15.2.�The Computer Name Panel.">“The Computer Name Panel.”</a>.
31
31
</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">
32
</p></li><li class="step" title="Step 5"><p>
33
33
Click on <span class="guimenu">Change</span>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
34
34
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>.
35
35
</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">
36
</p></li><li class="step" title="Step 6"><p>
37
37
Enter the name <span class="guimenu">MIDEARTH</span> in the field below the Domain radio button.
39
39
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>.
40
40
</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">
41
</p></li><li class="step" title="Step 7"><p>
42
42
Now click the <span class="guimenu">OK</span> button. A dialog box should appear to allow you to provide the credentials (username and password)
43
43
of a domain administrative account that has the rights to add machines to the domain.
45
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>.
45
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>.
46
46
</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">
47
</p></li><li class="step" title="Step 8"><p>
48
48
Click <span class="guimenu">OK</span>.
50
The “<span class="quote">Welcome to the MIDEARTH domain</span>” dialog box should appear. At this point, the machine must be rebooted.
50
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.
51
51
Joining the domain is now complete.
52
52
</p></li></ol></div><p>
53
<a class="indexterm" name="id2621845"></a>
54
<a class="indexterm" name="id2621852"></a>
53
<a class="indexterm" name="id2627903"></a>
54
<a class="indexterm" name="id2627910"></a>
55
55
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
56
56
panel in which you can set (or change) the Primary DNS suffix of the computer. This is a parameter that mainly affects members
57
57
of Microsoft Active Directory. Active Directory is heavily oriented around the DNS namespace.
59
<a class="indexterm" name="id2621878"></a>
60
<a class="indexterm" name="id2621885"></a>
59
<a class="indexterm" name="id2627936"></a>
60
<a class="indexterm" name="id2627943"></a>
61
61
Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers
62
62
register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server
63
63
to find the services (like which machines are domain controllers or which machines have the Netlogon service running).
65
<a class="indexterm" name="id2621903"></a>
65
<a class="indexterm" name="id2627962"></a>
66
66
The default setting of the Primary DNS suffix is the Active Directory domain name. When you change the Primary DNS suffix,
67
67
this does not affect domain membership, but it can break network browsing and the ability to resolve your computer name to
68
68
a valid IP address.
70
70
The Primary DNS suffix parameter principally affects MS Windows clients that are members of an Active Directory domain.
71
71
Where the client is a member of a Samba domain, it is preferable to leave this field blank.
73
<a class="indexterm" name="id2621927"></a>
74
According to Microsoft documentation, “<span class="quote">If this computer belongs to a group with <code class="constant">Group Policy</code>
73
<a class="indexterm" name="id2627985"></a>
74
According to Microsoft documentation, <span class="quote">“<span class="quote">If this computer belongs to a group with <code class="constant">Group Policy</code>
75
75
enabled on <code class="literal">Primary DNS suffice of this computer</code>, the string specified in the Group Policy is used
76
76
as the primary DNS suffix and you might need to restart your computer to view the correct setting. The local setting is
77
used only if Group Policy is disabled or unspecified.</span>”
78
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2621955"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id2621962"></a><a class="indexterm" name="id2621970"></a><a class="indexterm" name="id2621978"></a>
77
used only if Group Policy is disabled or unspecified.</span>”</span>
78
</p></div><div class="sect1" title="Samba System File Location"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2628013"></a>Samba System File Location</h2></div></div></div><p><a class="indexterm" name="id2628020"></a><a class="indexterm" name="id2628028"></a><a class="indexterm" name="id2628036"></a>
79
79
One of the frustrations expressed by subscribers to the Samba mailing lists revolves around the choice of where the default Samba Team
80
80
build and installation process locates its Samba files. The location, chosen in the early 1990s, for the default installation is
81
81
in the <code class="filename">/usr/local/samba</code> directory. This is a perfectly reasonable location, particularly given all the other
84
84
Several UNIX vendors, and Linux vendors in particular, elected to locate the Samba files in a location other than the Samba Team
86
</p><p><a class="indexterm" name="id2622014"></a><a class="indexterm" name="id2622025"></a><a class="indexterm" name="id2622033"></a><a class="indexterm" name="id2622045"></a><a class="indexterm" name="id2622052"></a><a class="indexterm" name="id2622064"></a><a class="indexterm" name="id2622072"></a><a class="indexterm" name="id2622080"></a><a class="indexterm" name="id2622088"></a><a class="indexterm" name="id2622095"></a><a class="indexterm" name="id2622103"></a><a class="indexterm" name="id2622111"></a><a class="indexterm" name="id2622119"></a><a class="indexterm" name="id2622127"></a><a class="indexterm" name="id2622135"></a><a class="indexterm" name="id2622143"></a>
86
</p><p><a class="indexterm" name="id2628072"></a><a class="indexterm" name="id2628084"></a><a class="indexterm" name="id2628092"></a><a class="indexterm" name="id2628103"></a><a class="indexterm" name="id2628111"></a><a class="indexterm" name="id2628123"></a><a class="indexterm" name="id2628130"></a><a class="indexterm" name="id2628138"></a><a class="indexterm" name="id2628146"></a><a class="indexterm" name="id2628154"></a><a class="indexterm" name="id2628162"></a><a class="indexterm" name="id2628170"></a><a class="indexterm" name="id2628178"></a><a class="indexterm" name="id2628186"></a><a class="indexterm" name="id2628194"></a><a class="indexterm" name="id2628202"></a>
87
87
Linux vendors, working in conjunction with the Free Standards Group (FSG), Linux Standards Base (LSB), and File Hierarchy
88
88
System (FHS), have elected to locate the configuration files under the <code class="filename">/etc/samba</code> directory, common binary
89
89
files (those used by users) in the <code class="filename">/usr/bin</code> directory, and the administrative files (daemons) in the
92
92
<code class="filename">/usr/share/swat</code>. There are additional support files for <code class="literal">smbd</code> in the
93
93
<code class="filename">/usr/lib/samba</code> directory tree. The files located there include the dynamically loadable modules for the
94
94
passdb backend as well as for the VFS modules.
95
</p><p><a class="indexterm" name="id2622212"></a><a class="indexterm" name="id2622220"></a><a class="indexterm" name="id2622228"></a>
95
</p><p><a class="indexterm" name="id2628271"></a><a class="indexterm" name="id2628279"></a><a class="indexterm" name="id2628287"></a>
96
96
Samba creates runtime control files and generates log files. The runtime control files (tdb and dat files) are stored in
97
97
the <code class="filename">/var/lib/samba</code> directory. Log files are created in <code class="filename">/var/log/samba.</code>
99
99
When Samba is built and installed using the default Samba Team process, all files are located under the
100
100
<code class="filename">/usr/local/samba</code> directory tree. This makes it simple to find the files that Samba owns.
101
</p><p><a class="indexterm" name="id2622267"></a>
101
</p><p><a class="indexterm" name="id2628325"></a>
102
102
One way to find the Samba files that are installed on your UNIX/Linux system is to search for the location
103
103
of all files called <code class="literal">smbd</code>. Here is an example:
104
104
</p><pre class="screen">
143
143
samba3-doc-3.0.20-1
144
144
samba3-client-3.0.20-1
145
145
samba3-cifsmount-3.0.20-1
146
</pre><p><a class="indexterm" name="id2622362"></a>
146
</pre><p><a class="indexterm" name="id2628421"></a>
147
147
The package names, of course, vary according to how the vendor, or the binary package builder, prepared them.
148
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622376"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id2622382"></a>
148
</p></div><div class="sect1" title="Starting Samba"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2628434"></a>Starting Samba</h2></div></div></div><p><a class="indexterm" name="id2628441"></a>
149
149
Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
150
150
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
151
151
are three daemons, two of which are needed as a minimum.
188
188
</pre></div></div><br class="example-break"><div class="variablelist"><dl><dt><span class="term">nmbd</span></dt><dd><p>
189
<a class="indexterm" name="id2622445"></a>
190
<a class="indexterm" name="id2622452"></a>
189
<a class="indexterm" name="id2628504"></a>
190
<a class="indexterm" name="id2628511"></a>
191
191
This daemon handles all name registration and resolution requests. It is the primary vehicle involved
192
192
in network browsing. It handles all UDP-based protocols. The <code class="literal">nmbd</code> daemon should
193
193
be the first command started as part of the Samba startup process.
194
194
</p></dd><dt><span class="term">smbd</span></dt><dd><p>
195
<a class="indexterm" name="id2622482"></a>
196
<a class="indexterm" name="id2622488"></a>
195
<a class="indexterm" name="id2628540"></a>
196
<a class="indexterm" name="id2628547"></a>
197
197
This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
198
198
manages local authentication. It should be started immediately following the startup of <code class="literal">nmbd</code>.
199
199
</p></dd><dt><span class="term">winbindd</span></dt><dd><p>
200
<a class="indexterm" name="id2622517"></a>
201
<a class="indexterm" name="id2622524"></a>
200
<a class="indexterm" name="id2628576"></a>
201
<a class="indexterm" name="id2628582"></a>
202
202
This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
203
203
Samba has trust relationships with another domain. The <code class="literal">winbindd</code> daemon will check the
204
204
<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
252
echo "Usage: smb {start|stop|restart|status}"
255
</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2622637"></a>
255
</pre></div></div><br class="example-break"><p><a class="indexterm" name="id2628696"></a>
256
256
SUSE Linux implements individual control over each Samba daemon. A Samba control script that can be conveniently
257
257
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
258
258
<code class="filename">/sbin</code> in a file called <code class="filename">samba</code>. This type of control script should be
259
259
owned by user root and group root, and set so that only root can execute it.
260
</p><p><a class="indexterm" name="id2622672"></a>
260
</p><p><a class="indexterm" name="id2628731"></a>
261
261
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>.
262
262
This file could be located in the directory <code class="filename">/etc/rc.d</code> and can be called
263
263
<code class="filename">samba</code>. A similar startup script is required to control <code class="literal">winbind</code>.
264
264
If you want to find more information regarding startup scripts please refer to the packaging section of
265
265
the Samba source code distribution tarball. The packaging files for each platform include a
266
266
startup control file.
267
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2622715"></a>DNS Configuration Files</h2></div></div></div><p>
267
</p></div><div class="sect1" title="DNS Configuration Files"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2628774"></a>DNS Configuration Files</h2></div></div></div><p>
268
268
The following files are common to all DNS server configurations. Rather than repeat them multiple times, they
269
269
are presented here for general reference.
270
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622727"></a>The Forward Zone File for the Loopback Adaptor</h3></div></div></div><p>
270
</p><div class="sect2" title="The Forward Zone File for the Loopback Adaptor"><div class="titlepage"><div><div><h3 class="title"><a name="id2628786"></a>The Forward Zone File for the Loopback Adaptor</h3></div></div></div><p>
271
271
The forward zone file for the loopback address never changes. An example file is shown
272
272
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
273
273
physical interface on the machine itself is routed to the loopback adaptor. This is
344
344
. 3600000 NS M.ROOT-SERVERS.NET.
345
345
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
347
</pre></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622916"></a>DNS Root Server Hint File</h3></div></div></div><p>
347
</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="id2628974"></a>DNS Root Server Hint File</h3></div></div></div><p>
348
348
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.
349
349
Periodically this file should be updated from the source shown. Because
350
350
of its size, this file is located at the end of this chapter.
351
</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="id2622947"></a><a class="indexterm" name="id2622958"></a>
351
</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="id2629005"></a><a class="indexterm" name="id2629016"></a>
352
352
The following procedure may be used as an alternative means of configuring
353
353
the initial LDAP database. Many administrators prefer to have greater control
354
354
over how system files get configured.
355
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2622975"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id2622982"></a><a class="indexterm" name="id2622990"></a><a class="indexterm" name="id2623001"></a>
355
</p><div class="sect2" title="Initialization of the LDAP Database"><div class="titlepage"><div><div><h3 class="title"><a name="id2629033"></a>Initialization of the LDAP Database</h3></div></div></div><p><a class="indexterm" name="id2629040"></a><a class="indexterm" name="id2629048"></a><a class="indexterm" name="id2629060"></a>
356
356
The first step to get the LDAP server ready for action is to create the LDIF file from
357
357
which the LDAP database will be preloaded. This is necessary to create the containers
358
358
into which the user, group, and other accounts are written. It is also necessary to
359
359
preload the well-known Windows NT Domain Groups, as they must have the correct SID so
360
360
that they can be recognized as special NT Groups by the MS Windows clients.
361
</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>
361
</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>
362
362
Create a directory in which to store the files you use to generate
363
363
the LDAP LDIF file for your system. Execute the following:
364
364
</p><pre class="screen">
366
366
<code class="prompt">root# </code> chown root:root /etc/openldap/SambaInit
367
367
<code class="prompt">root# </code> chmod 700 /etc/openldap/SambaInit
369
</p></li><li class="step" title="Step 2"><p>
370
370
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>,
371
371
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
372
372
<code class="filename">/etc/openldap/SambaInit/SMBLDAP-ldif-preconfig.sh.</code> These three files are,
373
373
respectively, parts A, B, and C of the <code class="filename">SMBLDAP-ldif-preconfig.sh</code> file.
374
</p></li><li class="step" title="Step 3"><p>
375
375
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
376
376
<code class="filename">/etc/openldap/SambaInit/.</code> These two files are
377
377
parts A and B, respectively, of the <code class="filename">init-ldif.pat</code> file.
378
</p></li><li class="step" title="Step 4"><p>
379
379
Change to the <code class="filename">/etc/openldap/SambaInit</code> directory. Execute the following:
380
380
</p><pre class="screen">
381
381
<code class="prompt">root# </code> sh SMBLDAP-ldif-preconfig.sh
466
466
modifyTimestamp: 20031217055747Z
467
467
entryCSN: 2003121705:57:47Z#0x000a#0#0000
469
</p></li><li class="step" title="Step 6"><p>
470
470
Your LDAP database is ready for testing. You can now start the LDAP server
471
471
using the system tool for your Linux operating system. For SUSE Linux, you can
472
472
do this as follows:
473
473
</p><pre class="screen">
474
474
<code class="prompt">root# </code> rcldap start
476
</p></li><li class="step" title="Step 7"><p>
477
477
It is now a good idea to validate that the LDAP server is running correctly.
478
478
Execute the following:
479
479
</p><pre class="screen">
705
705
sambaGroupType: 2
706
706
displayName: Domain Users
707
707
description: Domain Users
708
</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="id2623561"></a>The LDAP Account Manager</h2></div></div></div><p>
709
<a class="indexterm" name="id2623569"></a>
710
<a class="indexterm" name="id2623575"></a>
711
<a class="indexterm" name="id2623585"></a>
712
<a class="indexterm" name="id2623591"></a>
713
<a class="indexterm" name="id2623598"></a>
714
<a class="indexterm" name="id2623605"></a>
715
<a class="indexterm" name="id2623612"></a>
708
</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="id2629619"></a>The LDAP Account Manager</h2></div></div></div><p>
709
<a class="indexterm" name="id2629627"></a>
710
<a class="indexterm" name="id2629634"></a>
711
<a class="indexterm" name="id2629643"></a>
712
<a class="indexterm" name="id2629650"></a>
713
<a class="indexterm" name="id2629656"></a>
714
<a class="indexterm" name="id2629663"></a>
715
<a class="indexterm" name="id2629670"></a>
716
716
The LDAP Account Manager (LAM) is an application suite that has been written in PHP.
717
717
LAM can be used with any Web server that has PHP4 support. It connects to the LDAP
718
718
server either using unencrypted connections or via SSL/TLS. LAM can be used to manage
724
724
The current version of LAM is 0.4.9. Release of version 0.5 is expected in the third quarter
727
<a class="indexterm" name="id2623643"></a>
728
<a class="indexterm" name="id2623650"></a>
729
<a class="indexterm" name="id2623657"></a>
727
<a class="indexterm" name="id2629702"></a>
728
<a class="indexterm" name="id2629708"></a>
729
<a class="indexterm" name="id2629715"></a>
731
</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>
731
</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>
732
732
LAM is a useful tool that provides a simple Web-based device that can be used to
733
733
manage the contents of the LDAP directory to:
734
<a class="indexterm" name="id2623717"></a>
735
<a class="indexterm" name="id2623724"></a>
736
<a class="indexterm" name="id2623731"></a>
737
</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>
734
<a class="indexterm" name="id2629776"></a>
735
<a class="indexterm" name="id2629783"></a>
736
<a class="indexterm" name="id2629790"></a>
737
</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>
738
738
When correctly configured, LAM allows convenient management of UNIX (Posix) and Samba
739
739
user, group, and windows domain member machine accounts.
741
<a class="indexterm" name="id2623785"></a>
742
<a class="indexterm" name="id2623792"></a>
743
<a class="indexterm" name="id2623799"></a>
744
<a class="indexterm" name="id2623806"></a>
745
The default password is “<span class="quote">lam.</span>” It is highly recommended that you use only
741
<a class="indexterm" name="id2629844"></a>
742
<a class="indexterm" name="id2629851"></a>
743
<a class="indexterm" name="id2629858"></a>
744
<a class="indexterm" name="id2629864"></a>
745
The default password is <span class="quote">“<span class="quote">lam.</span>”</span> It is highly recommended that you use only
746
746
an SSL connection to your Web server for all remote operations involving LAM. If you
747
747
want secure connections, you must configure your Apache Web server to permit connections
748
748
to LAM using only SSL.
749
</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>
749
</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>
750
750
Extract the LAM package by untarring it as shown here:
751
751
</p><pre class="screen">
752
752
<code class="prompt">root# </code> tar xzf ldap-account-manager_0.4.9.tar.gz
755
755
</p><pre class="screen">
756
756
<code class="prompt">root# </code> dpkg -i ldap-account-manager_0.4.9.all.deb
758
</p></li><li class="step" title="Step 2"><p>
759
759
Copy the extracted files to the document root directory of your Web server.
760
760
For example, on SUSE Linux Enterprise Server 9, copy to the
761
761
<code class="filename">/srv/www/htdocs</code> directory.
763
<a class="indexterm" name="id2623886"></a>
762
</p></li><li class="step" title="Step 3"><p>
763
<a class="indexterm" name="id2629944"></a>
764
764
Set file permissions using the following commands:
765
765
</p><pre class="screen">
766
766
<code class="prompt">root# </code> chown -R wwwrun:www /srv/www/htdocs/lam
778
778
<code class="prompt">root# </code> cp config.cfg_sample config.cfg
779
779
<code class="prompt">root# </code> vi config.cfg
781
<a class="indexterm" name="id2623979"></a>
782
<a class="indexterm" name="id2623988"></a>
781
<a class="indexterm" name="id2630038"></a>
782
<a class="indexterm" name="id2630047"></a>
783
783
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>.
784
784
This is the minimum configuration that must be completed. The LAM profile
785
785
file can be created using a convenient wizard that is part of the LAM
786
786
configuration suite.
787
</p></li><li class="step" title="Step 5"><p>
788
788
Start your Web server then, using your Web browser, connect to
789
789
<a class="ulink" href="http://localhost/lam" target="_top">LAM</a> URL. Click on the
790
790
the <em class="parameter"><code>Configuration Login</code></em> link then click on the
794
794
<code class="filename">lam.conf</code> then, using your favorite editor,
795
795
change the settings to match local site needs.
796
796
</p></li></ol></div><p>
797
<a class="indexterm" name="id2624048"></a>
797
<a class="indexterm" name="id2630106"></a>
798
798
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>.
799
799
This file has been stripped of comments to keep the size small. The comments
800
800
and help information provided in the profile file that the wizard creates
802
802
Your configuration file obviously reflects the configuration options that
803
803
are preferred at your site.
805
<a class="indexterm" name="id2624071"></a>
805
<a class="indexterm" name="id2630130"></a>
806
806
It is important that your LDAP server is running at the time that LAM is
807
807
being configured. This permits you to validate correct operation.
808
808
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>.
809
809
</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>
810
<a class="indexterm" name="id2624134"></a>
810
<a class="indexterm" name="id2630192"></a>
811
811
The LAM configuration editor has a number of options that must be managed correctly.
812
812
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>.
813
813
It is important that you correctly set the minimum and maximum UID/GID values that are
817
817
the initial settings to be made. Do not forget to reset these to sensible values before
818
818
using LAM to add additional users and groups.
819
819
</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>
820
<a class="indexterm" name="id2624205"></a>
820
<a class="indexterm" name="id2630264"></a>
821
821
LAM has some nice, but unusual features. For example, one unexpected feature in most application
822
822
screens permits the generation of a PDF file that lists configuration information. This is a well
823
823
thought out facility. This option has been edited out of the following screen shots to conserve
826
<a class="indexterm" name="id2624220"></a>
826
<a class="indexterm" name="id2630279"></a>
827
827
When you log onto LAM the opening screen drops you right into the user manager as shown in
828
828
<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
829
829
to be used immediately. The editing of an existing user, as with the addition of a new user,
837
837
shows a sub-screen from the group editor that permits users to be assigned secondary group
839
839
</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>
840
<a class="indexterm" name="id2624400"></a><a class="indexterm" name="id2624406"></a>
840
<a class="indexterm" name="id2630459"></a><a class="indexterm" name="id2630464"></a>
841
841
The final screen presented here is one that you should not normally need to use. Host accounts will
842
842
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>
843
843
will, in most cases, not be used.
898
898
For further information regarding IMC refer to the web <a class="ulink" href="http://imc.sourceforge.net/" target="_top">site.</a>
899
899
Prebuilt RPM packages are also <a class="ulink" href="http://imc.sourceforge.net/download.html" target="_top">available.</a>
900
</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="id2624663"></a><a class="indexterm" name="id2624670"></a><p>
900
</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="id2630722"></a><a class="indexterm" name="id2630728"></a><p>
901
901
The setting of the SUID/SGID bits on the file or directory permissions flag has particular
902
902
consequences. If the file is executable and the SUID bit is set, it executes with the privilege
903
903
of (with the UID of) the owner of the file. For example, if you are logged onto a system as
968
968
drw-rw-r-- 2 bobj Domain Users 12346 Dec 18 18:11 maryvfile.txt
970
</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="id2624901"></a><a class="indexterm" name="id2624909"></a>
970
</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="id2630960"></a><a class="indexterm" name="id2630967"></a>
971
971
The integrity of shared data is often viewed as a particularly emotional issue, especially where
972
972
there are concurrent problems with multiuser data access. Contrary to the assertions of some who have
973
973
experienced problems in either area, the cause has nothing to do with the phases of the moons of Jupiter.
975
975
The solution to concurrent multiuser data access problems must consider three separate areas
976
from which the problem may stem:<a class="indexterm" name="id2624932"></a><a class="indexterm" name="id2624943"></a><a class="indexterm" name="id2624955"></a>
977
</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="id2624987"></a><a class="indexterm" name="id2624995"></a>
976
from which the problem may stem:<a class="indexterm" name="id2630990"></a><a class="indexterm" name="id2631002"></a><a class="indexterm" name="id2631013"></a>
977
</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="id2631046"></a><a class="indexterm" name="id2631054"></a>
978
978
Many database applications use some form of application-level access control. An example of one
979
979
well-known application that uses application-level locking is Microsoft Access. Detailed guidance
980
980
is provided here because this is the most common application for which problems have been reported.
981
</p><p><a class="indexterm" name="id2625012"></a><a class="indexterm" name="id2625020"></a>
981
</p><p><a class="indexterm" name="id2631070"></a><a class="indexterm" name="id2631078"></a>
982
982
Common applications that are affected by client- and server-side locking controls include MS
983
983
Excel and Act!. Important locking guidance is provided here.
984
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625032"></a>Microsoft Access</h3></div></div></div><p>
984
</p><div class="sect2" title="Microsoft Access"><div class="titlepage"><div><div><h3 class="title"><a name="id2631091"></a>Microsoft Access</h3></div></div></div><p>
985
985
The best advice that can be given is to carefully read the Microsoft knowledgebase articles that
986
986
cover this area. Examples of relevant documents include:
987
</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="id2625059"></a><a class="indexterm" name="id2625071"></a>
987
</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="id2631118"></a><a class="indexterm" name="id2631129"></a>
988
988
Make sure that your MS Access database file is configured for multiuser access (not set for
989
989
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>.
991
991
You can configure MS Access file sharing behavior as follows: click <span class="guimenu">[tab] Advanced</span>.
992
Set:<a class="indexterm" name="id2625122"></a>
993
</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="id2625151"></a>
992
Set:<a class="indexterm" name="id2631180"></a>
993
</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="id2631209"></a>
994
994
You must now commit the changes so that they will take effect. To do so, click
995
995
<span class="guimenu">Apply</span><span class="guimenu">Ok</span>. At this point, you should exit MS Access, restart
996
996
it, and then validate that these settings have not changed.
997
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625180"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id2625186"></a><a class="indexterm" name="id2625194"></a>
997
</p></div><div class="sect2" title="Act! Database Sharing"><div class="titlepage"><div><div><h3 class="title"><a name="id2631238"></a>Act! Database Sharing</h3></div></div></div><p><a class="indexterm" name="id2631245"></a><a class="indexterm" name="id2631253"></a>
998
998
Where the server sharing the ACT! database(s) is running Samba,or Windows NT, 200x, or XP, you
999
999
must disable opportunistic locking on the server and all workstations. Failure to do so
1000
1000
results in data corruption. This information is available from the Act! Web site
1002
1002
<a class="ulink" href="http://itdomino.saleslogix.com/act.nsf/docid/1998223162925" target="_top">1998223162925</a>
1003
1003
as well as from article
1004
1004
<a class="ulink" href="http://itdomino.saleslogix.com/act.nsf/docid/200110485036" target="_top">200110485036</a>.
1005
</p><p><a class="indexterm" name="id2625225"></a><a class="indexterm" name="id2625233"></a>
1005
</p><p><a class="indexterm" name="id2631283"></a><a class="indexterm" name="id2631291"></a>
1006
1006
These documents clearly state that opportunistic locking must be disabled on both
1007
1007
the server (Samba in the case we are interested in here), as well as on every workstation
1008
1008
from which the centrally shared Act! database will be accessed. Act! provides
1010
1010
registry settings that may otherwise interfere with the operation of Act!
1011
1011
Registered Act! users may download this utility from the Act! Web
1012
1012
<a class="ulink" href="http://www.act.com/support/updates/index.cfm" target="_top">site.</a>
1013
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625264"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id2625271"></a>
1013
</p></div><div class="sect2" title="Opportunistic Locking Controls"><div class="titlepage"><div><div><h3 class="title"><a name="id2631322"></a>Opportunistic Locking Controls</h3></div></div></div><p><a class="indexterm" name="id2631330"></a>
1014
1014
Third-party Windows applications may not be compatible with the use of opportunistic file
1015
and record locking. For applications that are known not to be compatible,<sup>[<a name="id2625283" href="#ftn.id2625283" class="footnote">14</a>]</sup> oplock
1015
and record locking. For applications that are known not to be compatible,<sup>[<a name="id2631342" href="#ftn.id2631342" class="footnote">14</a>]</sup> oplock
1016
1016
support may need to be disabled both on the Samba server and on the Windows workstations.
1017
</p><p><a class="indexterm" name="id2625297"></a><a class="indexterm" name="id2625305"></a><a class="indexterm" name="id2625313"></a>
1017
</p><p><a class="indexterm" name="id2631356"></a><a class="indexterm" name="id2631364"></a><a class="indexterm" name="id2631372"></a>
1018
1018
Oplocks enable a Windows client to cache parts of a file that are being
1019
1019
edited. Another windows client may then request to open the file with the
1020
1020
ability to write to it. The server will then ask the original workstation
1021
1021
that had the file open with a write lock to release its lock. Before
1022
1022
doing so, that workstation must flush the file from cache memory to the
1023
1023
disk or network drive.
1024
</p><p><a class="indexterm" name="id2625334"></a>
1024
</p><p><a class="indexterm" name="id2631393"></a>
1025
1025
Disabling of Oplocks usage may require server and client changes.
1026
1026
Oplocks may be disabled by file, by file pattern, on the share, or on the
added
removed
docs/htmldocs/Samba3-ByExample/appendix.html
