I got it to work! With your great help it wasn't that bad, or maybe I'm a
better sysadmin than I'm giving myself credit for. ;)
There were two steps, really. After creating the fstab line, I typed sudo
systemctl edit memcached.service. I entered this and saved:
[Service]
KillSignal=SIGUSR1
Absolutely. That's exactly the workflow it's designed for, we just haven't
updated any of the systemd scripts to be more friendly for it.
Also a caveat; there _was_ a bug fixed relatively recently with the
restart code. I don't know if ubuntu backports these. If you use large
objects (> 512k)
That's extremely helpful, thank you so much for this! I will look into it and
test on my staging server. I don't think systemd has ever killed or restarted
the process apart from once before I upgraded the RAM, so I'm not too worried
about the daily usage. But even systemd supports custom kill
Hey,
I might have to look at how ubuntu's install works.. it might not be set
up for this.
These are the basic steps for a restart:
1) set up memcached as you did, tmpfs/etc.
2) when you want to stop gracefully, issue a `kill -SIGUSR1 $(pidof
memcached)`
(kill is the command to send signals to
My site runs on one webserver and we rely heavily on memcached to make it
snappy, to the extent that a reboot will make the site unresponsive for
hours. So imagine my joy when I saw the warm restart addition, and the fact
that Ubuntu Server 20.04 LTS has a new enough version in its repo.
But
