[Digikam-devel] [digikam] [Bug 318902] very long lasting search for new items after copy of sqlite3 database

[krienke at uni-koblenz.de]

https://bugs.kde.org/show_bug.cgi?id=318902

--- Comment #2 from krienke at uni-koblenz.de ---
Just tested what files are modified by the sync (ls -lR). It is as it should
be, only the files that really changed on the source side as well as the parent
directory show a change in mtime on the destination side as well as the digikam
database file. All other files and directories remain untouched.

After the sync I started an strace  -v -f -F -e 'trace=open' on the digikam
process that again started a long lasting search for new entries. I could see
that each and every photo is beeing opened not only the modified ones or those
in a directory with a changed mtime.

-- 
You are receiving this mail because:
You are the assignee for the bug.