A linux box on our network is a samba server for a few clients
(Samba 2.28 on Mandrake Linux 9.2). I am not sure how the file
locking mechanism is working. What I want is that if one user has
opened a file for read and write, that file should not be
available to other users for writing (reading maybe yes).
However this does not seem to be happening. A file opened by
OOwriter on a linux system can also be opened and saved by a
windoze machine running that other word processing application.
However if another windoze machine tries to use the same file, the
word processor on it will display a message "file can be opened
read-only". What exactly is going on?
Reproduced below are excerpts from smb.conf related to locking:
****************
kernel oplocks = Yes
lock spin count = 3
lock spin time = 10
oplock break wait time = 0
.. ..
blocking locks = Yes
csc policy = manual
fake oplocks = No
locking = Yes
oplocks = No
level2 oplocks = No
oplock contention limit = 2
posix locking = Yes
strict locking = Yes
*****************
Will be grateful for help on this one. I have not been able to
understand after reading samba docs
Pramathesh
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
linux-india-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
