The unfortunate aspect is that both are implemented only in Windows
operating systems, and on Server, only for machines accessing the
share point using SMB. Hence, any Mac accessing a file using AFP or
SMB will not know about the locking and may modify the contents of
the file without warning.
So that leaves "Strict on, Oplock off" as the only choice for a mixed
mac/win environment, right?
Or would "S on, O on" allow the use of a file using oplock for an XP
machine and lock it for mac clients at the same time, because strict
is set, too? Doesn't make sense, I'm afraid... unless we have
hierarchic locking here?!
Besides, at this time the only way to activate strict locking seems
to be using "sudo sharing -e ShareName -t 1" in terminal.
Cheers
--
Christian Schmitz
Berlin, Germany
----------------------------------------------------
Paradise is exactly like where you are right now
only much, much better - Laurie Anderson
----------------------------------------------------
Klick: http://spezial-o-mat.de
----------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
