https://bugs.freedesktop.org/show_bug.cgi?id=41442
Roger Heflin <rahhori...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rahhori...@yahoo.com
--- Comment #10 from Roger Heflin <rahhori...@yahoo.com> ---
(In reply to comment #8)
> This seems like a feasible enhancement request. Going to go ahead and
> confirm the request, I don't know how easy it will be to implement but
> marking as a low level enhancement request.
>
> Rationale: Not many people will ever use the feature to disable the ability
> to lock files. Also, not sure how one would accidentally lock a file and
> then another person not want it locked (if I'm understanding this
> correctly). The simple thing to do is just not lock files. In a corporate
> setting I can see the feature being a little more useful.
>
> Thanks for putting in the request
Lock files only work in a *PERFECT* world te way they are implemented in
openoffice, and there is no what to easily fix things if that *PERFECT* world
fails.
Situation: machine opens a file on an NFS mount, office locks the file. Office
crashes, machine crashes or machine runs out of battery, X windows
crashs...probably other possible things that can happen...lock is left on NFS
server orphaned with no chance of reclaim/releasing/removing the lock without
using other tools to clear the file or copying the file to a new name and
working on it, or rebooting things in the correct manner.
Suggest when complaining about a lock existing on a file you need to explain
and/or give a way to clear/reset/bypass the lock. Office appears to have at
least 2 different methods and neither of the methods indicate how to reset the
lock (the *LCK file and the nfs locks), or give a way to reset the lock if the
user in question has the privs needed to reset the lock.
I have successfully cleared NFS locks but it takes an expert to even figure out
that is what is going wrong as nothing indicates which manner of locking is
being used.
There does not appear to be a way to disable this badly implemented/poorly
though out feature when the world is less than perfect, and there is no easy
way to clear/reclaim/remove a lock once office has applied it.
And if you disable NFS locking (at the NFS level) office refuses to open
anything as it cannot get a lock but appears to not be smart enough realize it
won't ever be able to get a lock, and there does not appear to be a working way
to disable the poorly though out feature in office any more.
This *BUG* is a mess, and from the number of posts about it I bet is annoying
just about all users of office and NFS as the condition required to cause to be
a problem is a common condition and once you hit the condition a pain to work
around, and there does not appear to be a working way to disable it.
I cannot agree with importance Low...this one is a seriously annoying bug on a
poorly though out feature.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
