On 2014-07-02 23:05, Shenandoah Gallitz wrote:
I'm importing some large email folders that have been converted from PST using ReadPST. Usually the import works correctly, but I have one folder of .EMLs where Pilerimport -d is stopping on a particular email and not going any further. I'm not sure which email is the culprit and this folder has over 50,000 emails on it. I can see the list of emails that Piler has successfully imported before the one it's stopping on, but I don't see any pattern -- Piler isn't importing sorted by filename, filesize, inode number, time/date stamp, etc. How does pilerimport -d determine the order of the files to import? I'd really like to find out which one of these EMLs are causing pilerimport to freeze.
well, pilerimport uses the standars readdir() calls to get the next directory entry, so in whatever order it presents the files to piler, it uses that way. However the reason for a freeze could be a misbehaving external helper that has a hard time to finish with an attachment in a timely fashion. Janos
