To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95014
                 Issue #|95014
                 Summary|Cannot lock file using sshfs shares
               Component|framework
                 Version|OOo 2.4.1 RC2
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|www
             Assigned to|mba
             Reported by|cjeanneret





------- Additional comments from [EMAIL PROTECTED] Thu Oct 16 13:32:09 +0000 
2008 -------
Hello,

I was reading a lot of stuff on "how OOo locks file" when we use shared file 
system.
Here's our situation:
we have a fileserver with an sshd server; our users mount directories through
SSHFS (which uses fuse).
Then, one of them, say A, open a file, say Foo.odt.
Permissions are : rw-srw-r (so that group can edit it without problem)

Then, a second one, say B, decides to open Foo.odt too.

And there's the big trouble : Foo.odt is NOT locked by A!

-> so if B edits it, saves it, then A saves his own modifications, B's
modifications aren't there anymore.

As far as I read, OOo uses OS lock system, and knows how to use samba/webdav
lock system too....
What I'm wondering is : why don't use a system like, say, vim? it "simply" puts
a ".filename.swp" near the file we opened, and removes it when we close the 
file.
In case we want to open this file twice, the second is read-only.

Note: we want to use sshfs, as it's really faster than samba, and we don't have
other OS than Linux/MacOS, which both know how to manage sshfs.

Thanks in advance, this point is "the" point of failure in our system...

---------------------------------------------------------------------
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