To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104974
User gwr changed the following:
What |Old value |New value
================================================================================
CC|'' |'gwr'
--------------------------------------------------------------------------------
------- Additional comments from g...@openoffice.org Tue Dec 8 18:39:29 +0000
2009 -------
This defect has also been reported here:
http://defect.opensolaris.org/bz/show_bug.cgi?id=12831
and internal to Sun as bugster CR 6906597
Here's my evaluation note for that CR:
I ran StarOffice 9 (the version included in snv_127) twice,
once re-saving a file on an smbfs mount, and again re-saving
a file on a tmpfs mount. In both cases, I used truss to log
system call activity, i.e. "truss -p $pid -o $outfile".
The two files are: soffice-tmpfs.truss, soffice-smbfs.truss
Both were edited to remove all but the relevant section.
Comparing the two truss outputs, we can see that StarOffice
is trying to mmap(2) a file in the smbfs mount point, which
returns ENOSYS because smbfs(7fs) does not support mmap.
One might be tempted to close this as a duplicate of CR
6565851 [mmap support for CIFS client (and use page cache)]
but this IS arguably the fault of OpenOffice. Here's why:
mmap(2) system call can and sometimes does return ENOSYS,
both in smbfs and other file systems, and applications are
expected to fall back to use of read/write instead.
Unfortunately, many applications assume mmap(2) can be used
on all files in all filesystems and don't bother to implement
any fallback path for cases where mmap is not supported.
OpenOffice is not the first to fail here. Many GNOME
applications also incorrectly assume mmap always works.
Someday, we hope to implement CR 6565851 for smbfs, and then
this problem will again be mostly not exposed, but this is
still really a bug in these applications.
---------------------------------------------------------------------
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...@sc.openoffice.org
For additional commands, e-mail: issues-h...@sc.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
