MobileRead Forums - View Single Post

unboggling · 07-31-2011, 06:58 PM

Kovid, OK. Thanks for the help. The debugger and comparisons of logs led to narrowing down the problem, very useful. I'll await further help and while awaiting, think about it.

I'm stumped. I know I can probably solve the problem temporarily by either (1) moving Add and Main to external drive, or (2) leaving them where they are on internal and assigning everyone rw permission on all files. But (1) would run slightly slower in file manipulation and I'm not sure how new files would be handled permission-wise; and (2) is definitely temporary - I know any new-add formats, opfs & cvrs will end up with the old faulty permissions. Why they are faulty in the first place is the primary question.

One other thing I can think of that might relate and cause problems: I have 2 macs wirelessly networked. Mac1 has MyAccountA as the username. Mac2 has MyAccountA as the username (the same exact name). OSX treats those as 2 different names (each needing it's own file permissions) - Mac1MyAccountA and Mac2MyAccountA. I have made a supreme effort the past 2 months to keep Mac2's me away from Mac1's internal drive calibre files. Mac2's me and Mac2's calibre only access a copy of a backup file that stays untouched by Mac1 me and Mac1 calibre. That way calibre doesn't bawk at the different accounts trying to use the same library db or files and the 2 usernames' library file permissions don't get mixed up. I have calibre instances running on both computers, one accessing/showing the copy of a backup of Main and the other accessing/showing Add. This permits me to work on Add and easily refer back to author, series, etc metadata in Main on side by side computers. A couple months ago I learned the hard way not to let the two calibre instances touch the same instance of a library serially or simultaneously. At that time I fixed (I thought) the resulting mess in permissions and discrepancies in opfs and metadatadb. Since then I have been extremely careful and am 99.9% sure the 2 instances have not crossed swords or messed with each others' files.

07-31-2011, 06:58 PM	#19
unboggling Wizard Posts: 1,065 Karma: 858115 Join Date: Jan 2011 Device: Kobo Clara, Kindle Paperwhite 10	Kovid, OK. Thanks for the help. The debugger and comparisons of logs led to narrowing down the problem, very useful. I'll await further help and while awaiting, think about it. I'm stumped. I know I can probably solve the problem temporarily by either (1) moving Add and Main to external drive, or (2) leaving them where they are on internal and assigning everyone rw permission on all files. But (1) would run slightly slower in file manipulation and I'm not sure how new files would be handled permission-wise; and (2) is definitely temporary - I know any new-add formats, opfs & cvrs will end up with the old faulty permissions. Why they are faulty in the first place is the primary question. One other thing I can think of that might relate and cause problems: I have 2 macs wirelessly networked. Mac1 has MyAccountA as the username. Mac2 has MyAccountA as the username (the same exact name). OSX treats those as 2 different names (each needing it's own file permissions) - Mac1MyAccountA and Mac2MyAccountA. I have made a supreme effort the past 2 months to keep Mac2's me away from Mac1's internal drive calibre files. Mac2's me and Mac2's calibre only access a copy of a backup file that stays untouched by Mac1 me and Mac1 calibre. That way calibre doesn't bawk at the different accounts trying to use the same library db or files and the 2 usernames' library file permissions don't get mixed up. I have calibre instances running on both computers, one accessing/showing the copy of a backup of Main and the other accessing/showing Add. This permits me to work on Add and easily refer back to author, series, etc metadata in Main on side by side computers. A couple months ago I learned the hard way not to let the two calibre instances touch the same instance of a library serially or simultaneously. At that time I fixed (I thought) the resulting mess in permissions and discrepancies in opfs and metadatadb. Since then I have been extremely careful and am 99.9% sure the 2 instances have not crossed swords or messed with each others' files. Last edited by unboggling; 07-31-2011 at 07:21 PM.