> I kicked the scan off again, having tinkered with log settings, but the > second time it seems to be scanning okay. Any idea why? >
I've seen cases, too, where an aborted scan left the DB in an odd state. And where I had to trigger more than one rescan to clean up the mess. Or delete the db files... _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
