On 12/07/2019 06:16 PM, Gene Heskett wrote: > I'm forced to agree. But if I have to do that, its likely I'll just jump > ship to claws or even (spit) t-bird. This has been bugging me off and > on for at least 5 years, and I've been mostly ignored, sent hundreds of > crash reports all to no avail as far as solving the problem is > concerned. Paypal has no clue who Tim is, so I've not been able to > contribute, which bothers the hell outta me as a firm believer in > TANSTAAFL. Not having paid my dues, I don't feel like I can demand. Yes, I've followed on and off your kmail woes. From what you describe this is a bug that should be fixed. kmail should not continually be putting a load on the system resorting indexes, etc.. There should be debugging that can be cranked up to cause TDE to spit out INFO level messages for kmail that may give a better picture of what is going on. If the problem is that your mail store is too big for kmail to handle without thinking it needs to reindex -- that's still a bug and whether it is a Qt3 issue or kmail issue, both should be solveable today. (just off hand I can see if a limit is INT_MAX how a 20G mail store would be an issue), Regardless, whatever it triggering the reindexing needs to be identified. Whatever was burning up the cores on your old box -- is still causing the same mischief on your new box -- it's just doing a whole lot more mischief a whole lot faster now.... -- David C. Rankin, J.D.,P.E. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
