Go back to the db folder and see how much bigger the db files are now.
File size doesn't really tell anything about the scan process. Files grow because it's cheaper to append than to re-use etc. But that's a DB thing, not limited to LMS.
But *dont* do a *vacuum* even with the LMS stopped - after that the db is completly bad - in case of lms show strange things somewhere.
What's that? If vacuum was so badly broken, sqlite would be badly broken. Vacuum is a DB level command and therefore must be totally transparent to the application using it. I recently even wrote a small plugin to run vacuum from inside LMS. I yet have to see any negative effect.
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
