[Kde-pim] Is it possible to postpone the start of the Akonadi server?

Andreas Gungl a.gungl at gmx.de
Fri Jan 3 15:24:32 GMT 2014


Am Donnerstag, 2. Januar 2014, 14:57:05 schrieb Kevin Krammer:
> On Thursday, 2014-01-02, 11:10:44, Andreas Gungl wrote:
> > Hello,
> > 
> > When I start KDE, the initialization of the Akonadi server takes some time
> > with heavy disk activity. I wonder if I can somehow configure to start the
> > server only when the first application (usually KMail in my case) starts.
> > Often I don't need a PIM application, and I'd like to avoid that start
> > procedure to get faster to the things I really want to work on.
> 
> That is actually what it does.
> Akonadi is not autostarted nor restored on session restore. It is started by
> its clients on demand.
> 
> Basically, when an Akonadi client initializes a session with the Akonadi
> server, it will either connect to the running instance or start it if it is
> not running yet.
> 
> Assuming that your distributor didn't add an autostart script or similar to
> start Akonadi on login, this would indicate that some program that is part
> of your session startup is an Akonadi client and thus triggers Akonadi
> startup.
> 
> Unfortunately it seems to be impossible to get the connected applications
> from the socket in the file system, i.e. netstat or fuser will only list
> akonadiserver.
> 
> I think we currently have no direct way to list all open sessions either :(
> 
> What you could try is to run Akonadiconsole after login, enable the debugger
> and then restart Akonadi.
> All clients should attempt re-establish their connection and their sessions
> should show up as tabs. That would be Akonadiconsole itself, all resources
> and agents and if you are lucky the client that caused the startup.

It turned out the Digital Clock applet was the cause (as supposed by Daniel). 
I've changed the setting as recommended and now it works fine.

> > I've tried to set StartServer=false in the
> > ~/.config/akonadi/akonadiserverrc file, but that prevents a server start
> > totally. That means, if I then try a manual "akonadictl start", it fails
> > until I revert to StartServer=true in the config file.
> 
> That setting is actually unrelated. It is part of the MySQL configuration,
> used to determine wether Akonadiserver should run its own mysqld instance or
> connect to an externally started one.

Ah, good to know. And thanks for the feedback.

Best regards,
Andreas

-- 
Kindermode Online - Fashion for Kids
http://www.theofeel.de
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/



More information about the kde-pim mailing list