What i found out:
The logfiles are quite big (2x64m) and the datafiles itself pretty small.
So an adjustment of mysql is neccessary to get rid of that:
-rw-rw---- 1 gaelic users 64M Sep 24 18:58 ib_logfile0
-rw-rw---- 1 gaelic users 64M Sep 21 21:12 ib_logfile1
in mysql.conf of the akonadi dir just change
innodb_log_file_size=64M
to
innodb_log_file_size=8M
I hope no problems will arise with that change ...
On 9/23/10, Werner LEMBERG <wl@xxxxxxx> wrote:
>
>>> I'm about to quit kde and rename the dir, as I'm just switching to
>>> the sqlite driver from the mysql driver, and see what happens.
>>
>> It worked fine, altho I did have to start akonaditray and add a new
>> contacts resource, pointing it at the appropriate dir containing
>> kaddressbook's vcfs (the default was some other location), then
>> restart kde again, for it to fully take effect (with just an akonadi
>> restart, kaddressbook could see the new resource but not fully load
>> it, but a full kde restart fixed that).
>
> Well, these are interesting observations, but it still doesn't help me
> in stopping akonadi to fill the .local/share/akonadi tree with
> approx. 150MByte ï#| I don't want that stuff!
>
> Is anybody here who can tell me how to *really* disable akonadi? This
> is, to make kdeinit not start akonadi (since this causes the creation
> of the 150MByte data if it doesn't exist yet, and this slows down the
> start-up enormously).
>
>
> Werner
>
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
