On 10/30/2010 12:36 PM, Tanstaafl wrote:
On 2010-10-29 5:20 PM, JOE Conner wrote:
Lock files are created to prevent two or more different users from
editing the same file at the same time, and interfering with each
other's edits.
I know that - but OOo obviously used to determine this differently,
because it *used* to work fine.
It *used* to have a problem allowing multiple people to edit a file
simultaneously. This problem was *real* and desperately needed fixing.
It makes no sense to have the lock file saved differently on your
machine, as this would permit the simultaneous edits that are trying
to be prevented in the first place.
Actually, that is true... what I want is for OOo to *fall-back* to the
previous method it used for determining if a file was already opened for
editing when it is unable to create the lock file.
To solve your problem, get your IT department to set your write
permissions properly. It sounds as if you have EDIT but not CREATE
flags set.
*I* am the IT department, and the permissions *are* set properly. I want
certain users to be able to *edit* documents that reside in directories
that they do *not* have the ability to create *new* documents in.
As I said, it worked properly like this for *years* prior to OOo
starting to use lock files like MSO does. Another example of a step
*backwards* in the name of 'progress'.
Since *you* are the *IT* department, then you have within your own power
to solve your problem.
It seems to me that the lock file was a much sought after solution, and
it is you who are requesting a regression.
That being said it seems to me that the solution is in fixing the file
permissions to properly allow the
creation of the lock file and proproperly training the people who would
edit the file that they have no *authority*
to create any other files and to have suitable penalties established for
violators.
A second solution, one *you would like*, would be for the file locking
to follow some other procedure other than creating a lock file in the
first place. Perhaps by automatically changing the file ownership to
only the person editing the file and then automatically restoring the
ownership to the original settings when the file is closed. I am not
sure what to do about an abnormal file close.
Joe Conner, Poulsbo, WA USA
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
