I have the same problem, and it makes me wonder.. Who has 100MB
addresses and PIM-data anyway? Perhaps some default setting is a
little bit larger than strictly neccessary (and efficient)?
I don't know what triggers akonadi at login. Perhaps it is related
to nepomukservices also consuming 100%
Hi Sturle,
On Dienstag, 7. Dezember 2010, Sturle Sunde wrote:
An equaly large problem for me is that those 100MiB are database log
files are invalidated when the user log out and akonadi stops. New
files are created at each login, wasting huge amounts of space in my
nilfs2 based backup.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
holger: I did mention that i had not tested the issue myself. only
observed talk on #ltsp regarding the issue.
Klausade did note the cpu usage and disk consumtion, when logging in the
first time. Is there something special in our debian-edu setup
Hi Ronny,
On Montag, 6. Dezember 2010, Ronny Aasen wrote:
holger: I did mention that i had not tested the issue myself. only
observed talk on #ltsp regarding the issue.
Ah :) I'm not surprised and glad I added a disclaimer ;-)
I think we need to test this more :)
Oh yeah!
cheers,
package: akonadi
severity: important
x-debbugs-cc: debian-...@lists.debian.org
user: debian-...@lists.debian.org
usertag: debian-edu
Hi,
when logging into KDE4, akonadi starts indexing, which uses all cpu for about
a minute. After that, the users homedirectory is about 100mb in size.
When 20
reassign 606016 debian-edu
thanks
Hi,
from my discussion with the akonadi maintainer:
h01ger is there a way to turn off akonadi globally? its unusable when 20
users log into a ltsp server at the same time.. not everybody is running kde4
on her own laptop
svuorela just remove it.
svuorela
6 matches
Mail list logo
