To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=99682
                 Issue #|99682
                 Summary|Strange behavior when opening files from NFS share
               Component|framework
                 Version|OOo 3.0.1
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|dicr_oo





------- Additional comments from [email protected] Thu Feb 26 16:37:17 
+0000 2009 -------
Situation:

NFS server - Mandriva 2006. Provides some share/, using "all_squash" (treats all
clients as anonymous users).
NFS client - Mandriva 2008.1, Czech OO 3.0.1. from official RPMs.

Now let's have a NFS directory "share/", which contains text document
"file.odt". Owner/group is always "nobody"/"nogroup".

1) Permissions: share/ - "drwxrwxr-x", file.odt - "-rw-rw-r--". OO opens file
read-only.
2) Permissions: share/ - "drwxrwxr-x", file.odt - "-rw-rw-rw-". OO opens file
normally, lock file is created.
3) Permissions: share/ - "drwx------", file.odt - "-rw-rw-r--". OO opens file
read-only.
4) Permissions: share/ - "drwx------", file.odt - "-rw-------". OO opens file
normally, lock file is created.

Why is that? I mean, it should work fine with all four combinations, right? And
with OO 2.4.1, it does...

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