Configuration Control Issue

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Configuration Control Issue

chuck ef
So, as I mentioned in an earlier email, I bought a new iMac and it is using 10.14.1 (Mojave). I have been in the process of setting it up with files from the old iMac. I use two backup eternal drives (for redundancy). I just today put those files onto the new machine (USB-C is wonderful).


As it happens, there are two versions, different dates,  of a spreadsheet (an .ods file) with the same name - in two separate folders, associated with one backup drive or the other. I opened up the one with the older date (as it happened) to address an earlier issue identified another OO user (jerky scrolling in Mojave). I closed that file and tried to open up the other version (with a newer date but same name, though different folder) - I get a message that this file is locked by me blah blah blah - do I want read-only, copy, cancel?


Never happened before. I tried quitting OO but that did not release the file; I went back to the older-date version to see if there is something I can do to release it. Nothing.


Maybe reboot?


Not a big deal in any sense but I am curious about what OO is doing since these are two different files (different dates, different paths) - the only similarity is the name.


Thanks.
Reply | Threaded
Open this post in threaded view
|

Re: Configuration Control Issue

Keith N. McKenna
On 11/1/2018 6:44 PM, chuck ef wrote:

> So, as I mentioned in an earlier email, I bought a new iMac and it is using 10.14.1 (Mojave). I have been in the process of setting it up with files from the old iMac. I use two backup eternal drives (for redundancy). I just today put those files onto the new machine (USB-C is wonderful).
>
>
> As it happens, there are two versions, different dates,  of a spreadsheet (an .ods file) with the same name - in two separate folders, associated with one backup drive or the other. I opened up the one with the older date (as it happened) to address an earlier issue identified another OO user (jerky scrolling in Mojave). I closed that file and tried to open up the other version (with a newer date but same name, though different folder) - I get a message that this file is locked by me blah blah blah - do I want read-only, copy, cancel?
>
>
> Never happened before. I tried quitting OO but that did not release the file; I went back to the older-date version to see if there is something I can do to release it. Nothing.
>
>
> Maybe reboot?
>
>
> Not a big deal in any sense but I am curious about what OO is doing since these are two different files (different dates, different paths) - the only similarity is the name.
>
>
> Thanks.
>
It sounds like AOO did not release the lock file for some reason. The
first think to do s check the directories on each disk that you opened
the file from and see if there is a file of the form.~lck.filename.ods.
If you find one delete it and then try to open the file again.

If there is none or deleting it does not work reply back to the list
with that information and someone will try to walk you through other
possibilities.

Please reply only yo the list address at mailto:[hidden email]

Regards
Keith


signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Configuration Control Issue

chuck ef
A reply to Keith McKenna.


Found it. Things work fine. This was just an intellectual issue for me - the work around was trivial.


I have never actually tested one of these backup files - I simply copied them to the drives. Installing the files onto this new machine was a first. Somehow, I don't understand it, but somehow those "lock" files came with the .ods files themselves. There were actually several in different backup folders.


For other Mac users, the cmd + shift + "." keys make hidden files visible in Finder.


You can also find them in a terminal window but this was easier.


Thanks.


________________________________
From: Keith N. McKenna <[hidden email]>
Sent: Thursday, November 1, 2018 9:40 PM
To: [hidden email]
Subject: Re: Configuration Control Issue

On 11/1/2018 6:44 PM, chuck ef wrote:

> So, as I mentioned in an earlier email, I bought a new iMac and it is using 10.14.1 (Mojave). I have been in the process of setting it up with files from the old iMac. I use two backup eternal drives (for redundancy). I just today put those files onto the new machine (USB-C is wonderful).
>
>
> As it happens, there are two versions, different dates,  of a spreadsheet (an .ods file) with the same name - in two separate folders, associated with one backup drive or the other. I opened up the one with the older date (as it happened) to address an earlier issue identified another OO user (jerky scrolling in Mojave). I closed that file and tried to open up the other version (with a newer date but same name, though different folder) - I get a message that this file is locked by me blah blah blah - do I want read-only, copy, cancel?
>
>
> Never happened before. I tried quitting OO but that did not release the file; I went back to the older-date version to see if there is something I can do to release it. Nothing.
>
>
> Maybe reboot?
>
>
> Not a big deal in any sense but I am curious about what OO is doing since these are two different files (different dates, different paths) - the only similarity is the name.
>
>
> Thanks.
>
It sounds like AOO did not release the lock file for some reason. The
first think to do s check the directories on each disk that you opened
the file from and see if there is a file of the form.~lck.filename.ods.
If you find one delete it and then try to open the file again.

If there is none or deleting it does not work reply back to the list
with that information and someone will try to walk you through other
possibilities.

Please reply only yo the list address at mailto:[hidden email]

Regards
Keith

Reply | Threaded
Open this post in threaded view
|

Re: Configuration Control Issue

Keith N. McKenna
On 11/2/2018 6:11 PM, chuck ef wrote:

> A reply to Keith McKenna.
>
>
> Found it. Things work fine. This was just an intellectual issue for me - the work around was trivial.
>
>
> I have never actually tested one of these backup files - I simply copied them to the drives. Installing the files onto this new machine was a first. Somehow, I don't understand it, but somehow those "lock" files came with the .ods files themselves. There were actually several in different backup folders.
>
>
> For other Mac users, the cmd + shift + "." keys make hidden files visible in Finder.
>
>
> You can also find them in a terminal window but this was easier.
>
>
> Thanks.
<snip>
Just to satisfy the intellectual curiosity the .lck files are not backup
files. They are created every time a file is opened in AOO and are used
Lock the file by being opened for write by someone else. The only reason
one should be left behind is if AOO terminated abnormally. The most
common reasons are because of a power surge or power failure or by
closing the on a laptop before AOO has finished all it internal clean
up. Glad we were able to solve your problem.

Regards
Keith



signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Configuration Control Issue

chuck ef
Oh I understood their purpose from your previous email (although it seems like an odd way to do CM - seems like that should be handled outside of the app). I was just not aware of their existence.

I have no idea why the backup process is capturing them, although they are not as hidden as one might suspect. I suspect I am doing something incorrectly.

As for the reason you gave below, those are exceedingly uncommon on my end - so it is a mystery to me why so many were left behind.

I know that OO would often crash when I would try to open it the first years I used it - but I long ago made the app open up at boot up. It only rarely crashes now, and never while I am editing the .ods files.  So I do not know where they all came from.

It’s just interesting to me - and a reminder to try the backup files once in a while.




On Nov 3, 2018, at 3:28 PM, Keith N. McKenna <[hidden email]<mailto:[hidden email]>> wrote:

On 11/2/2018 6:11 PM, chuck ef wrote:
A reply to Keith McKenna.


Found it. Things work fine. This was just an intellectual issue for me - the work around was trivial.


I have never actually tested one of these backup files - I simply copied them to the drives. Installing the files onto this new machine was a first. Somehow, I don't understand it, but somehow those "lock" files came with the .ods files themselves. There were actually several in different backup folders.


For other Mac users, the cmd + shift + "." keys make hidden files visible in Finder.


You can also find them in a terminal window but this was easier.


Thanks.
<snip>
Just to satisfy the intellectual curiosity the .lck files are not backup
files. They are created every time a file is opened in AOO and are used
Lock the file by being opened for write by someone else. The only reason
one should be left behind is if AOO terminated abnormally. The most
common reasons are because of a power surge or power failure or by
closing the on a laptop before AOO has finished all it internal clean
up. Glad we were able to solve your problem.

Regards
Keith