Hello
I want to ask something - how I can turn off Akonadi autostart in Slackware 13.0 ?
Thanks
p.s. excuse me for the mistakes but my English is awful

System Settings > Advanced > Akonadi Configuration. Stop the Akonadi server. Unfortunately, dependent applications will autostart it, however you could remove all of its resources.

There is no option to stop it.
In Akonadi Resources Configuration is only one message: Akonadi not operational
In Akonadi Server Configuration under Status is: The Akonadi server is not running

Is it the "automatic migration" that you are trying to disable?

I too want to permanently turn off Akonadi autostart in Slackware 13.0 but it keeps on resurfacing. If "dependent applications" will revive it against my will, I need to know what those "dependent applications" are, so they too can be permanently disabled.

Anyone able to help or offer useful advice?

If it is not running when you check for that it means that the setup is not working correctly (otherwise it would be running when requested to start).

From the description I would also assume it is triggered by the migration tool.

See http://techbase.kde.org/Projects/PIM/Ak ... amework.3F

Cheers,
_

this failure that continues to come up is fixed in slackware-current, there were additional innodb embedding flags needed. you should be safe to pull the mysql-5.1.39 in slackware-current
this will allow akonadi to complete then you can disable it successfully.

Could you add, or point to, a more complete explanation of how to remove Akonadi?

I've gotten it mostly turned off in Slackware 13, but I still see error messages when I exit X that suggest *something* from that mess is still running.

There's another issue, and I don't know if it's related.

I've run Slackware for years, but only as a CLI-only server. I've occasionally started X (KDE) but only as a lark, and I've never 'worked' in KDE. I've done web development in a Win2K or XP box with Samba shares to the web directory on a test server running Apache, PHP, & MySQL

However, recently I have been running in KDE on a daily basis. There are some benefits, but memory performance sucks. I have 3 Gb RAM. As configured, Slack 13 with Bind, MySQL, Apache, Samba, & Squid running consumes about 220MB RAM under low (home office) load. On load, X w/ KDE4 consumes about 600MB RAM. This climbs to near 1 GB after a day's use. But, if I don't reboot after a couple of days, I'm left with 50MB free and an active swap file!

By contrast, I can run WinXP SP3 for a week, with little or no memory creep, and with all apps closed RAM consumption of around 350MB, even after days of use.

Are Akonadi / Neopmuk / Strigi the cause of the KDE4 memory leakage? Or is it something else? If it's the Akonadi mess, then I really, really want to find out how to root it out of my system.

GaHillBilly

GaHillBilly wrote:Could you add, or point to, a more complete explanation of how to remove Akonadi?

I've gotten it mostly turned off in Slackware 13, but I still see error messages when I exit X that suggest *something* from that mess is still running.

you can always got to the system settings -> Akonadi Configuration -> then the Akonadi server Configuration and uncheck the "Use internal MySQL server" and Apply, then recheck it, and apply. this way it resets it, and akonadi can do its thing without the errors you are seeing on the console.
as for completely removing it, this an assumed dependency of KDE, hence its in the kdesupport group to be available when compiling KDE. This is how the pre-compiled packages come from slackware, and if you want to compile the packages yourself, see the source/ directory of the install repo of the respective version you have installed.

GaHillBilly wrote:There's another issue, and I don't know if it's related.

I've run Slackware for years, but only as a CLI-only server. I've occasionally started X (KDE) but only as a lark, and I've never 'worked' in KDE. I've done web development in a Win2K or XP box with Samba shares to the web directory on a test server running Apache, PHP, & MySQL

However, recently I have been running in KDE on a daily basis. There are some benefits, but memory performance sucks. I have 3 Gb RAM. As configured, Slack 13 with Bind, MySQL, Apache, Samba, & Squid running consumes about 220MB RAM under low (home office) load. On load, X w/ KDE4 consumes about 600MB RAM. This climbs to near 1 GB after a day's use. But, if I don't reboot after a couple of days, I'm left with 50MB free and an active swap file!

By contrast, I can run WinXP SP3 for a week, with little or no memory creep, and with all apps closed RAM consumption of around 350MB, even after days of use.

Are Akonadi / Neopmuk / Strigi the cause of the KDE4 memory leakage? Or is it something else? If it's the Akonadi mess, then I really, really want to find out how to root it out of my system.

GaHillBilly

There are more things involved there than just these kdesupport components. if you look at top, and sort on mem, you'll see the primary culprits. in my case its X, with compositing and dual-head i'm expecting it though. and firefox it there at the top of the list. this machine as been going for weeks also, and has numerous things going on its still only at 1091 of 2009 mb of mem usage, so i'm not sure what other factors you may have off setting this. if you want more assistance with those questions though, see http://www.linuxquestions.org/questions/slackware-14/ as it is the official forum for slackware questions.

Take care,

vb

Hm-m-mh. Last first:

Regarding mem leaks, "top" isn't much help, because the memory I'm 'losing' isn't being actively used by anything. In other words, I can kill everything, and memory usage remains high. It even remains high once I *leave* X, and return the CLI. That's why I'm assuming it's some sort of leak, that marks areas of RAM as in-use, when they're not.

Regarding Akonadi, I don't want to stop the error messages, I want to stop it from running in any way. If I understand you correctly, there's really no way to do so, without re-compiling KDE.

What would be the real-time, functional cost of an Akonadi / Nepomuk-free version of KDE4?

GaHillBilly

If you wish to find out where memory usage is going, try Exmap.

This sounds like your system is acting in a completely expected manner and caching files in memory so it doesn't have to re-read them ( Windows does this as well, but its caching is nowhere near as aggressive as a Linux system )

Remember that it doesn't matter if only 50mb is free if you have 1.5gb of caches.

Code: Select all

ben@grace:~> free -m
             total       used       free     shared    buffers     cached
Mem:           490        471         19          0          9        229
-/+ buffers/cache:        231        258
Swap:         2055        185       1869

My system has 9mb of disk buffers, and 229mb of disk caches currently, so is therefore only actually using 231mb of memory, with 185mb additionally on swap.

GaHillBilly wrote:It even remains high once I *leave* X, and return the CLI.

Which means it is not caused by the applications associated with the X session, since they are termined as well and the kernel has reclaimed all resources associated with them.

After a couple of days I often see some swap being used and that's a good thing. It means stuff which is not needed is removed (relocated to swap) from memory and the new free memory can be used for increasing efficiency, e.g. I/O buffers.

Cheers,
_

I understand the swap thing, sorta.

But I should have added some other information: what caused me to look at mem usage in the first place was Firefox turning to mud and getting dead slow to start up. If swap was working as you suggest, I would have expected it to get faster, since it was all cached / swapped / what not.

Regardless, all gets 'fixed' with a cold reboot.

GaHillBilly

PS. Thanks for the tip on Exmap. I've downloaded it, and will compile it.

I noticed some fairly severe cautions about its use, though. Have you experienced lockup or data loss when using it?

GaHillBilly

I have not experienced in lockups while using it. Note that it requires an X session to use.