mirror of
https://github.com/samba-team/samba.git
synced 2025-03-08 04:58:40 +03:00
corrected it's (it is) documentation errors, when "its" should be
being used. lkcl (This used to be commit 7cd640e5b1a6bbe13834fe23a23ef03117024f0e)
This commit is contained in:
parent
ef0b39006e
commit
5c2d12119c
@ -28,7 +28,7 @@ allows you to access a SMB printer (such as one attached to an OS/2 or
|
||||
WfWg server) from Unix, using an entry in /etc/printcap, or by
|
||||
explicitly specifying the command used to print files.
|
||||
|
||||
What are it's features?
|
||||
What are its features?
|
||||
------------------------
|
||||
|
||||
Samba supports many features that are not supported in other SMB
|
||||
|
@ -85,7 +85,7 @@ To syncronize your PC's clock with your Samba server:
|
||||
</UL>
|
||||
|
||||
Each time you start your computer (or login for Win95) your PC will
|
||||
synchronize it's clock with your Samba server.</P>
|
||||
synchronize its clock with your Samba server.</P>
|
||||
<P>Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba
|
||||
- see:
|
||||
<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/BROWSING.txt">BROWSING.txt</A> *** for more information.</P>
|
||||
|
@ -570,7 +570,7 @@ To syncronize your PC's clock with your Samba server:
|
||||
<item> Close the properties dialog box by choosing 'OK'
|
||||
</itemize>
|
||||
Each time you start your computer (or login for Win95) your PC will
|
||||
synchronize it's clock with your Samba server.
|
||||
synchronize its clock with your Samba server.
|
||||
|
||||
Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba
|
||||
- see: <url url="ftp://samba.anu.edu.au/pub/samba/docs/BROWSING.txt" name="BROWSING.txt"> *** for more information.
|
||||
|
@ -841,7 +841,7 @@
|
||||
o Close the properties dialog box by choosing 'OK'
|
||||
|
||||
Each time you start your computer (or login for Win95) your PC will
|
||||
synchronize it's clock with your Samba server.
|
||||
synchronize its clock with your Samba server.
|
||||
|
||||
Alternativley, if you clients support Domain Logons, you can setup
|
||||
Domain Logons with Samba - see: BROWSING.txt
|
||||
|
@ -112,7 +112,7 @@ code! I wrote back saying it was OK, but never heard from him again. I
|
||||
don't know if it went on the cd-rom.
|
||||
|
||||
Anyway, the next big event was in December 1993, when Dan again sent
|
||||
me an e-mail saying my server had "raised it's ugly head" on
|
||||
me an e-mail saying my server had "raised its ugly head" on
|
||||
comp.protocols.tcpip.ibmpc. I had a quick look on the group, and was
|
||||
surprised to see that there were people interested in this thing.
|
||||
|
||||
|
@ -605,7 +605,7 @@ To syncronize your PC's clock with your Samba server:
|
||||
* Close the properties dialog box by choosing 'OK'
|
||||
|
||||
Each time you start your computer (or login for Win95) your PC will
|
||||
synchronize it's clock with your Samba server.
|
||||
synchronize its clock with your Samba server.
|
||||
|
||||
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -320,7 +320,7 @@ all smb.conf files :
|
||||
wins server = <name or IP address>
|
||||
|
||||
where <name or IP address> is either the DNS name of the WINS server
|
||||
machine or it's IP address.
|
||||
machine or its IP address.
|
||||
|
||||
Note that this line MUST NOT BE SET in the smb.conf file of the Samba
|
||||
server acting as the WINS server itself. If you set both the
|
||||
@ -358,7 +358,7 @@ server as a domain master browser set the following option in the
|
||||
domain master = yes
|
||||
|
||||
The domain master browser should also preferrably be the local master
|
||||
browser for it's own subnet. In order to achieve this set the following
|
||||
browser for its own subnet. In order to achieve this set the following
|
||||
options in the [global] section of the smb.conf file :
|
||||
|
||||
domain master = yes
|
||||
|
@ -94,7 +94,7 @@ have at least one Backup Domain Controller (BDC).
|
||||
|
||||
The PDC and BDCs then participate in replication of the SAM database so that
|
||||
each Domain Controlling participant will have an up to date SAM component
|
||||
within it's registry.
|
||||
within its registry.
|
||||
|
||||
Samba can NOT at this time function as a Domain Controller for any of these
|
||||
security services, but like all other domain members can interact with the
|
||||
|
@ -48,10 +48,10 @@ Details:
|
||||
Windows NT checks at start up to see if any domain logon
|
||||
controllers are already running within the domain. It finds
|
||||
Samba claiming to offer the service and therefore does NOT
|
||||
start it's Network Logon Service.
|
||||
start its Network Logon Service.
|
||||
|
||||
Windows NT needs the Windows NT network logon service to gain
|
||||
from it's Domain controller's SAM database the security
|
||||
from its Domain controller's SAM database the security
|
||||
identifier for the user loging on.
|
||||
|
||||
Work-around: Stop the Samba nmbd and smbd processes, then on the Windows
|
||||
|
@ -37,7 +37,7 @@ only written and tested for AFS 3.3 and later.
|
||||
SECURITY = SERVER
|
||||
=================
|
||||
|
||||
Samba can use a remote server to do it's username/password
|
||||
Samba can use a remote server to do its username/password
|
||||
validation. This allows you to have one central machine (for example a
|
||||
NT box) control the passwords for the Unix box.
|
||||
|
||||
|
@ -88,7 +88,7 @@ passwords they are in trouble.
|
||||
Samba can try to cope with this by either using the "password level"
|
||||
option which causes Samba to try the offered password with up to the
|
||||
specified number of case changes, or by using the "password server"
|
||||
option which allows Samba to do it's validation via another machine
|
||||
option which allows Samba to do its validation via another machine
|
||||
(typically a WinNT server).
|
||||
|
||||
Samba supports the password encryption method used by SMB
|
||||
@ -128,7 +128,7 @@ The second major problem is the "opportunistic locking" requested by
|
||||
some clients. If a client requests opportunistic locking then it is
|
||||
asking the server to notify it if anyone else tries to do something on
|
||||
the same file, at which time the client will say if it is willing to
|
||||
give up it's lock. Unix has no simple way of implementing
|
||||
give up its lock. Unix has no simple way of implementing
|
||||
opportunistic locking, and currently Samba has no support for it.
|
||||
|
||||
Deny Modes
|
||||
|
@ -315,7 +315,7 @@ codes of locking calls to tell clients that everything is OK.
|
||||
|
||||
The second class of locking is the "deny modes". These are set by an
|
||||
application when it opens a file to determine what types of access
|
||||
should be allowed simultaneously with it's open. A client may ask for
|
||||
should be allowed simultaneously with its open. A client may ask for
|
||||
DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special
|
||||
compatability modes called DENY_FCB and DENY_DOS.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user