To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=57712


User hro changed the following:

                  What    |Old value                 |New value
================================================================================
                    Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
                Resolution|                          |WORKSFORME
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Tue Apr 18 08:59:21 -0700 
2006 -------
@dbw: Your desired behaviour reflects the DENY_xxx modes used by the 
Windows file API. UNIX does not support such DENY_xxx modes which are a kind 
of locking on Windows. Instead file locking is implemented (and OOo does so) by 
f_cntl() calls to set a write lock, while on Windows clients it's done by 
setting the 
share mode to DENY_WRITE when opening a file for writing.

Your first provided SMBD log output shows that the share mode is not set when 
accessing the files from linux clients. OOo does not know anything about the 
file 
system it accesses, it just sets a write lock. Then it's up to the smb client 
to 
forward the write lock to the smb server and the smbd has to translate that 
into a 
share mode (and vice versa when a share mode is set by a Windows client).

oplocking has nothing to do with real locking it's just a hint wether the 
client is 
allowed to cache the files by assuming the client is the only one accessing the 
file. So enabling oplocking in smb.conf is a bad idea if you want to get the 
desired 
exclusive file access. I don't know which parameter in smb.conf might help but 
when taking a look into the manpages I guess playing around with "posix 
locking", "kernel oplocks",  "strict locking" might be the right switches.

The answer for the NFS problem is that locking is just faked if there's no lock 
deamon running on the NFS server.

So the answer to fix the problem is: Configure your file system servers and 
clients 
in a suitable manner to get the desired behaviour. It's not an OOo specific 
thing. 
And I don't know wether this is possible at all as I've not tested the smb.conf 
switches.







---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to