Tanstaafl wrote:
On 2010-01-08 1:43 PM, Barbara Duprey wrote:
Well, it's far from elegant -- but you could copy the file to another
directory, make your changes, and copy back (losing the lock protection,
though, unless the working location is shared by everybody who edits the
file). Hope somebody comes up with a better solution, though!
That won't work, because the user doesn't have write perms in that
directory.
Sorry, I misunderstood -- you said "have write privs to the file
itself" so I thought you could write the same file back, just didn't
have "create" privs for the lock file. I've been seeing lock files for
quite a few versions now, I'm pretty sure for at least 2.4.1. I think
the name of the lock file might have changed, though. As I recall, it
used to be the OOo filename with .lock at the end. Maybe the new name is
triggering something the old one didn't?
This is an administrative share, where most users have read-only perms,
but a few users have the ability to edit certain documents in certain
subdirectories.
Like I said, this used to work until recently. I think it broke in
either 3.0 or 3.1... I can go install some old versions and figure out
which one broke it, but I was hoping someone would know off the top of
their head.
I think it is related to the NEW behavior of OOo creating the 'locking'
file like MSO has always done. It didn't used to do that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
