27 Nov
2018
27 Nov
'18
8:20 p.m.
On Tuesday 27 November 2018 01:53:39 pm Gene Heskett wrote:
On Tuesday 27 November 2018 14:06:54 Michael wrote:
Hey Gene,
The odds of me having non KMail files, or no longer supported file fomats,
there are really high, as I've manually transported the KMail directories
back from Mandrake to OpenSUSU, to ???, to CentOS, to Ubuntu...
On Tuesday 27 November 2018 05:44:56 am Dr.
Nikolaus Klepp wrote:
I think I may have found the cause of that, I tried to run claws and it
made some non-kmail files in the kmail Mail corpus. I deleted them and
while I have had the advisory since but never the hour+ long cpu burn as
seen by htop. 4 or 5 seconds after closing the advisory and its ready to
work again. Am Dienstag, 27. November 2018 schrieb dep:
Ah, probably goes without saying, but KMail seems really twitchy
during start up when rebuilding (or loading?) its indexes. Basically
check top to see if it's finished. On my system it'll suck up a full
CPU for 5 to 20 minutes and is almost guaranteed to crash if I try to
do anything in KMail until it's finished.
Best,
Michael greets, folks . . .
is there a reliable, nondestructive way to force kmail to reindex
a mail subdirectory?
thanks.
Yes, just delete the index files *.index *.index.ids *.index.sorted.
When you restart kmail, it'll rebuild the indices. If you want to be
on the save side, create a copy of your mail folder and then delete
the indices ... I use old faithfull, mc to look for and do the cleanup
.
What is this 'mc' you speak off? Has to be better than me doing a manual
scan ;)
Best,
Michael