To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=97442
                 Issue #|97442
                 Summary|Samba veto files directive breaks file locking
               Component|Word processor
                 Version|OOo 3.0
                Platform|PC
                     URL|
              OS/Version|Windows XP
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|open-import
             Assigned to|writerneedsconfirm
             Reported by|icefield





------- Additional comments from [email protected] Fri Dec 19 21:06:20 
+0000 2008 -------
Native odt files on a SAMBA share (Debian etch) open as read only with OOo 3
whereas they opened/saved without problem under OOo2.4

Issue seems to be the relatively common Samba directive:

veto files = /.*/

which is recommended in several Samba setup examples to prevent users
creating/deleting linux files beginning with a '.'

The problem is that the lock file format (.~lock.xxx.odt#) is created, but
cannot be listed/deleted. The user (and OOo) cannot see the lock file because it
is not visible even though it exists.

Hard to debug for the average user since the lock file is invisible on the
client side.

Can lock file name format be changed so that it does not have special meaning?
(e.g., try creating a file with the lock file format under Windows Explorer - it
fails)

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