To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53682
------- Additional comments from [EMAIL PROTECTED] Mon Sep 12 08:25:59 -0700 2005 ------- But you don't know *why* it commonly happens, right? My dilemma is as follows: Without further information under which conditions exactly this happens, it sounds to me like a bug in the kernel (or at least a deviation from Posix), and the patch looks like a workaround for that bug. However, on other platforms, where ENOLCK indicates the (unlikely) event of resource exhaustion, instead of "locking not supported" (which your comments imply that it does mean on recent Linux kernels), the workaround makes the code worse (silently ignoring the request to lock a file), not better. Hence, my reluctance to include it as-is. --------------------------------------------------------------------- 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]
