Quote:
Originally Posted by Patricius
But it appears there are two kinds of scenarios that causes the database corruption:
1. Calibre with kobo plugins (touch, touch_extend) and any running fmon process, after file transferred.
I've done the isolation test for this (without Koreader). Since KSM uses fmon, I consider the corruption with KSM is due to the same reason. Without the source, I don't know what exactly fmon does besides file-watching and process-spawning.
2. Kill the nickel after it have killed the on-animator, lauch koreader.sh and some transfers with Calibre after it brings back the nickel.
This is simply what my first modification does. I'm still a layman about nickel, maybe frostschutz would be kind enough to explain the reason of corruption in this case? I have no time to test upon this scenario in detail (without calibre/koreader, or even kill and relaunch nickel then do some transfers).
|
When nickel is started from KSM, there are still some scripts running that are located on the user partition (and in many cases instances of fmon). That being the case, the user partition cannot be unmounted when nickel connects via usb. This is not pretty, and becomes dangerous if (and I think, but am not sure, only if) files are modified that are currently in use (which seems to be the case with the database when one adds books with calibre.)