Presently the init & conf that come with the memcached ebuild lacks correct support for running memcached on a socket. This of course could always be worked around by using the MISC_OPTS included in the config file, but the init script still (incorrectly) warned that it was an insecure way of running memcached, when keeping it on a unix socket can be done more securely than network + firewall constraints. Attached is an update to the init and conf file for this service adding proper support for sockets. I also took this as an opportunity to fix the haphazard indentation and tidy it up. There is one potential issue with my changes, I have changed the location of the PID file to remove the PORT from it by default for two reasons. 1. When running memcached on a socket, there is no port 2. Multiple concurrent running versions of memcached already have their PIDs tagged with the CONF variable. I could not think of any use cases this may break but would appreciate feedback if I'm overlooking something. Reproducible: Always
Created attachment 364334 [details] init file
Created attachment 364336 [details] conf file
fixed in tree as 1.4.17
