To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=97139
User mav changed the following:
What |Old value |New value
================================================================================
CC|'jsk,ul' |'hro,jsk,mba,ul'
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Thu Dec 18 17:18:28 +0000
2008 -------
It looks like I can reproduce the problem now.
The reason seems to be the combination of O_EXCL and O_CREAT that are used to
create the lock file. Such an nfs mount does not allow to open the file using
the mentioned combination of flags. These flags are necessary to avoid the race
condition on document opening, so that the creation of the lock file fails in
case there is already one.
By the way, I have the same problem if I use OOo2.x and try to create a new file
on the problematic partition, the old office can not create a new .odt document
there.
OOo3.1 will allow in this case to open the file without OOo locking if system
file locking is active. If system file locking is not active the user will be
notified that no locking is active.
---------------------------------------------------------------------
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]
