David C. Rankin wrote: > 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.... I also think his archive is too big and also I think he's touching mails directly or with something else, causing the reindexing, although only hypothesis. It could be also a bug - but how can one reproduce it? regards --------------------------------------------------------------------- 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
