https://bugs.documentfoundation.org/show_bug.cgi?id=56544

--- Comment #22 from Stephan Bergmann <[email protected]> ---
(In reply to Tim Banchi from comment #18)
> so if a smb or webdav(?) share is mounted via the mount command (not via
> gvfs), LO still uses the .~lock.*# file for locking?

If an SMB share is mounted into the filesystem, LO will transparently see its
content with file URLs.

If an SMB share is accessed via GVfs, LO should see its content with smb URLs
(but could also see it with FUSE-based file URLs, e.g., when triggered from
Nautilus and LO's .desktop file wouldn't contain X-GIO-NoFuse=true).

> If I understand you right, that would not prevent the LOSS-UPDATE problem,
> because LO would not request a lock from the smb/webdav server (I don't know
> if that is possible).

LO has two concepts of "document locking."  Any given scenario can potentially
use none, one, or both of these.

One is to use LO's protocol of placing a .~lock.*# file next to the document. 
This is used for documents accessed via file, sftp, and (now) smb URLs (and
when writing a file next to the document is possible for LO, i.e., when it has
write access to the containing directory).  This of course only prevents
concurrent (i.e., potentially corrupting) modifications in cases where all
parties accessing the document do so by using this protocol.

The other is to use whatever locking mechanisms the URL scheme's access
protocol provides:

For file URLs on Linux, LO supports advisory fcntl(F_SETLK) locking.  How well
this works for remote filesystems (like NFS or Samba) mounted into the Linux
filesystem depends on further factors.  Again, this of course only prevents
concurrent (i.e., potentially corrupting) modifications in cases where all
parties accessing the document do so by using this protocol.

For smb URLs, no such protocol is used.

For webdav URLs, WebDAV's locking protocol should be used.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to