{"id":8558,"date":"2015-03-15T16:28:43","date_gmt":"2015-03-15T16:28:43","guid":{"rendered":"https:\/\/wp.okra.host\/article\/running-memcached\/"},"modified":"2021-03-07T14:30:12","modified_gmt":"2021-03-07T13:30:12","slug":"running-memcached","status":"publish","type":"ht_kb","link":"https:\/\/kb.okra.host\/de\/article\/running-memcached\/","title":{"rendered":"Ausf\u00fchren von Memcached"},"content":{"rendered":"

\u00dcbersicht<\/h2>\n

Memcached\u00a0is\u00a0an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.\u00a0It is available on newer platforms<\/a> (v6+) without any additional compilation<\/a> from source. Accounts with terminal access<\/a> are eligible to use Memcached.<\/p>\n

Schnellstart<\/h2>\n

From the Terminal<\/a>, run: memcached -l 127.0.0.1 -p PORT<\/code> where PORT is a preassigned port<\/a>\u00a0to the account.<\/p>\n

Hinweis:<\/strong><\/span> use 127.0.0.1 to prevent outside network activity. 127.0.0.1 will only allow traffic that originates from the same server. A better solution, if connecting solely from an app locally on the server\u00a0(WSGI<\/a>\/PHP\/CGI\/Schiene<\/a>, etc), is to specify -s\u00a0\/tmp\/memcached.sock<\/code> anstelle von -l<\/code>\/-p<\/code>\u00a0to specify a local UNIX domain socket instead of a TCP socket.<\/p>\n

Configuring & Daemonizing<\/h2>\n

Now with Memcached\u00a0up and running, you can create\u00a0a long-term solution that starts up with the server and always runs in the background.<\/p>\n

\n

Note<\/strong>: as with most files, any line that begins with a octothorpe\/pound\/hash symbol (#) denotes a comment. These are never interpreted by an application, but serve as guidance. The following\u00a0configuration omits these helpful comments for brevity.<\/p>\n<\/blockquote>\n

Once again, from the terminal run:\u00a0memcached -l 127.0.0.1 -p PORT -d -P \/tmp\/memcached.pid<\/code><\/p>\n

The only differences of note are introduction of -d<\/code> und -P<\/code> flags.\u00a0-d<\/code> daemonizes memcached to run in the background and\u00a0-P<\/code> saves the process identifier to a file called \/tmp\/memcached.pid<\/code>. This allows you to easily kill the memcached daemon if necessary:<\/p>\n

kill -9 $(cat \/tmp\/memcached.pid)<\/code><\/pre>\n
Starting on Start-up<\/h3>\n
    \n
  1. Visit Dev<\/strong> >\u00a0Task Scheduler<\/strong> innerhalb der Bedienfeld<\/a>\u00a0to schedule a new task.<\/li>\n
  2. Under\u00a0Command<\/strong>, enter memcached -l 127.0.0.1 -p PORT -d -P \/tmp\/memcached.pid<\/code><\/li>\n
  3. Under Scheduling<\/em>, select\u00a0Server Start<\/strong><\/li>\n
  4. Click\u00a0Add<\/strong><\/li>\n<\/ol>\n
    Siehe auch<\/h2>\n