Lame default for memcached in karmic

[Oli]

Binary package hint: memcached

By default memcached stops itself loading thanks to /etc/default/memcache
Additionally, you cannot load it through /etc/init.d/memcache for the same reason.

This is about as counter-intuitive as ubuntu gets. If somebody installs memcached, there's zero doubt they want to run it. It's sole purpose of being on a system is to run.

So there are two bugs here. Firstly, the default should be to run (just a tiny edit to the default needed) and secondly, even if the default is stopped, the user should be able to launch it manually through init.d

[ergo (ergo14)]

yeah, i had that too unfortunately and wasnt sure whats the problem

[ramorrismorris (morris-bob)]

The symptom for me was that my mediawiki installation came to a crawl immediately after upgrading to 9.10. The upgrade was a sequence from 8.04, 8.10, 9.04 and I didn't test mediawiki on the intermediate steps, so I am not sure if the upgrade path is implicated, or the karma upgrade itself. It's hard to imagine only a few reports of this issue if it were widespread.

Adjusting /etc/default/memcached to hold
<code>
ENABLE_MEMCACHED=yes
</code>
and restarting memcached seems to be satisfactory

[Brandon Helwig (brhelwig)]

I believe this also affects debian. Would be appropriate in this case to contact the upstream maintainer?