memcache on a dreamhack?

[kareila]

Does anyone have any tips for getting memcache to work on a dreamhack?

The instructions on the wiki assume you have root and can use apt-get.

Thanks in advance!

Comments

[exor674]

You probably need to work with sophie, as she'll need to assign you a port your memcached can work on and stuff.

[sophie]

So, as you know, we got you sorted for this. For anyone else who wants to use memcache on their Dreamhack:

* Let me or Fu (depending on whose box you're on) know, first, so you can be assigned a port that you can use for memcached.

* You'll then want to run memcached in a screen session, as it runs in the foreground. The command you want to run in screen is:

memcached -p <port>

where <port> is the port number you were given.

* Finally, you'll want to edit your etc/config-local.pl file. Look for this line:

#@MEMCACHE_SERVERS = ('hostname:port');

and change it to:

@MEMCACHE_SERVERS = ('127.0.0.1:<port>');

again replacing <port> with the appropriate port number. (Make sure also that the line is uncommented by removing the # at the front.)

This, I think, should be all that's needed.

[mark]

Why not run memcached with -d so it runs in the background? And you can specify -m to give it a small amount of memory.

memcached -d -m 8 -l 127.0.0.1 -p $PORT

[sophie]

I don't know much at all about memcached, so the parameters I gave were based on what Dre had said was necessary.

The -m switch is definitely a good idea in this case, as would the -l switch if it does what I think it does (since I assume that otherwise it'll listen on all interfaces?)

As for -d, for a dev installation I imagine it would be useful to see console messages easily, though I don't even know if memcached outputs any, heh. (I'd personally still do it in screen just for the ability to Ctrl-C it directly rather than having to kill via the command line, but that's totally a me-thing and I know that not everyone will want that.)

Thanks for the tips!

[mark]

Yeah, -l is "bind to IP". And you're right about the foreground! It doesn't by default but you can specify -v or -vv (or maybe -vvv) to get some very verbose output which can really help in debugging.