Akonadi/nl: Difference between revisions
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
Line 83: | Line 83: | ||
=== Migration problems === | === Migration problems === | ||
'''Akonadi's''' [[Special:myLanguage/Glossary#Akonadi|Glossary entry]] has a brief description of its purpose and other useful links. [[Special:myLanguage/Akonadi_and_AddressBook|This]] page explains how '''Akonadi''' and '''KAddressBook''' work together. | |||
=== High CPU or Memory usage === | === High CPU or Memory usage === |
Revision as of 14:30, 20 March 2013
Inleiding
In KDE SC 4.4 was KAddressBook het eerste programma dat gebruik ging maken van Akonadi. Vroeg in de overgang gaat dit tot aanloopproblemen leiden en de Gids voor het oplossen van problemen helpt bij het oplossen daarvan. In de woordenlijst wordt kort beschreven wat Akonadi is. Daar vindt u ook zinvolle verwijzingen naar meer informatie. Zodra de aanloopproblemen zijn opgelost, gaat Akonadi een krachtige ondersteuning voor veel programma's worden.
At the time of writing, the following applications are enabled to use the Akonadi framework to centrally store and access user data. Follow through to each application's page to learn more.
KMail
Mail Client Uses Akonadi to store emails
KAddressBook
Contact Manager Uses Akonadi to store contact information
KOrganizer
Personal Organizer Uses Akonadi to store calendars, events, journals, etc.
KJots
Note Taking Application Uses Akonadi to store notes
KAlarm
Personal alarm scheduler Uses Akonadi to store alarms
In addition to this, plasma widgets like the Digital Clock widget, the Notes widget also use Akonadi to store and retrieve events and notes.
Controlling the Akonadi server
The Akonadi control module in System Settings provides an easy means to starting, stopping, restarting and querying the status of the Akonadi server. You may also accomplish this from the commandline using the command akonadictl.
To start the Akonadi server,
akonadictl start
To stop the Akonadi server,
akonadictl stop
To restart a running Akonadi server,
akonadictl restart
To query the status of the Akonadi server,
akonadictl status
Disabling the Akonadi subsystem
The Akonadi server is launched automatically at login whenever any Akonadi-enabled application requests access to it.
To disable the Akonadi subsystem, first, shut down the running Akonadi server from the control module or the command line:
akonadictl stop
Now, edit the file ~/.config/akonadi/akonadiserverrc and change StartServer from true to false:
StartServer=false
The Akonadi server should no longer launch automatically on login.
Frequently Asked Questions
Where is my data now?
A full explanation of where the data is stored and Akonadi's interaction with it is available in Andras Mantia's blog
Migration problems
Akonadi's Glossary entry has a brief description of its purpose and other useful links. This page explains how Akonadi and KAddressBook work together.
High CPU or Memory usage
If you are experiencing 100% CPU usage by the virtuoso-t process when using Akonadi and related applications, try this proposed workaround while it is being investigated: In KRunner's configuration page, disable the Nepomuk search plugin and the Contact plugin. Then, log out and back in. For further information and inputs, report back here or on the Forum or on the IRC channel #kontact.
Akonadi and Nepomuk, why?
There is often a good deal of confusion about Akonadi and Nepomuk. Why data from Akonadi is indexed in Nepomuk explains exactly why we have both, and what their roles are. Don't miss the additional information from Will Stephenson in the Comments section.