On 2010-01-08 5:24 PM, Barbara Duprey wrote: > 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. Above, I should have said 'create' perms. The user has 'full control' of the file in question, but read-only access to the containing directory. This used to 'just work', but broke somwehere between 2.x and 3.1.1... > 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? Dunno... all I know for certain is this used to work, and now does not. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
