
Chapter 3 Administering Windows Users, Groups, Computers, and Share Points 41
Managing SMB Share Points
Share points for Windows home directories and roaming user profiles are set up
automatically on a Mac OS X Server primary domain controller (PDC), but you can set
up other share points. Windows uses the server message block (SMB) protocol to
access share points.
The default share point for Windows home directories is the same as the share
point for Mac OS X home directories. The default share point for user profiles is the
/Users/Profiles/ folder on the PDC server. (This SMB share point is not shown in
Workgroup Manager.) You can set up alternate SMB share points for home directories
and user profiles on the PDC server or on domain member servers.
You can set up additional share points for exclusive or nonexclusive use of Windows
users. For example, you could set up a share point where Windows and Mac OS users
save shared graphics or word processing files that can be used on either platform.
Conversely, you could set up a share point for SMB access only, so that Windows users
have a network location for files that can’t be used on other platforms.
For an overview of share points, including a discussion of issues you may want to
consider before creating them, see the share points chapter in the file services
administration guide.
Opportunistic Locking (oplocks)
SMB share points in Mac OS X Server support the improved performance offered by
opportunistic locking (“oplocks”).
In general, file locking prevents multiple clients from modifying the same information
at the same time; a client locks the file or part of the file to gain exclusive access.
Opportunistic locking grants this exclusive access but also allows the client to cache its
changes locally (on the client computer) for improved performance.
To enable oplocks, you change the Windows protocol settings for a share point using
Workgroup Manager.
Important: Do not enable oplocks for a share point that’s using any protocol other
than SMB.
Strict Locking
It’s normally the responsibility of a client application to see if a file is locked before it
tries to open it. A poorly written application may fail to check for locks, and could
corrupt a file already being used by someone else.
Strict locking, which is enabled by default, helps prevent this. When strict locking is
enabled, the SMB server itself checks for and enforces file locks.
LL2356.book Page 41 Thursday, September 4, 2003 3:21 PM
Kommentare zu diesen Handbüchern