From 5c2d12119c7d2e8c8563f22ffa23ab7d213242fb Mon Sep 17 00:00:00 2001 From: Samba Release Account Date: Tue, 26 Aug 1997 15:36:46 +0000 Subject: corrected it's (it is) documentation errors, when "its" should be being used. lkcl (This used to be commit 7cd640e5b1a6bbe13834fe23a23ef03117024f0e) --- docs/textdocs/UNIX-SMB.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/textdocs/UNIX-SMB.txt') diff --git a/docs/textdocs/UNIX-SMB.txt b/docs/textdocs/UNIX-SMB.txt index 88a7324dd7..ec2e657c05 100644 --- a/docs/textdocs/UNIX-SMB.txt +++ b/docs/textdocs/UNIX-SMB.txt @@ -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 -- cgit