To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=98343
------- Additional comments from m...@openoffice.org Sun Jan 25 23:22:02 +0000 2009 ------- The behavior is pretty correct. OOo3.0.x does not use system file locking at all, and own OOo3.0 lock is recognized only by OOo3.x offices. So the system, as well as any other application can change/remove the file. The problem is not always reproducible in OOo3.0 because the system filelocking still was used there sometimes by fault. The reason to get rid of system file locking is that it behaves itself inconsistently in heterogeneous networks. Later it was recognized that a lot of users need the system file locking more that the consistency of the file locking in the mentioned network configuration. For this reason OOo3.1 supports system file locking and own file locking by default, although the system file locking still can be turned off. Just to summarize, it is no bug for OOo3.0.x branch, since the behavior is as specified. The behavior should not be reproducible in default configuration of OOo3.1, since it uses system file locking per default. --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
