To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116690
User pegasus changed the following:
What |Old value |New value
================================================================================
Status|CLOSED |UNCONFIRMED
--------------------------------------------------------------------------------
Resolution|DUPLICATE |
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Fri Jan 28 16:23:37
+0000 2011 -------
I've read through #78897 and I don't agree with the findings there. "Not our
problem" is not a proper way to address real world problems. /tmp getting full
is a
real scenario, despite what those specifications say. And relying on a flawed
specs
is a bug by itself. It's OOo writer that is loosing user's data, not some spec
for
some theoretical OS. And as I've said before, user's data are holy and you
should do
everything in your power to keep them safe.
If your code really must go through /tmp to create&check lock files and to save
existing documents, there's a temp dir in the profile. What's that for anyway?
Also there are issues througout the issue tracker related to out of disk space
condition going as far back as I could search. The fact that they still pop up
shows
there's some ignorance and negligence going on regarding this problem and I
find this
unacceptable for a product such as Open Office.
---------------------------------------------------------------------
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]
