https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36492
--- Comment #1 from Marcel de Rooy <[email protected]> --- Changing the conf file is not the complete answer. Actually this fix from https://github.com/saz/puppet-memcached/issues/27 does it the other way around: mkdir /var/run/memcached chown memcache:memcache /var/run/memcached memcached.conf should (still) contain: -P /var/run/memcached/memcached.pid What happens now when stopping and starting? (Note that /etc/init.d/memcached stop does not work! Try: start-stop-daemon --stop --quiet --oknodo --retry 5 --name memcached) In var/run: -rw-r--r-- 1 root root 5 Apr 3 13:24 memcached.pid In var/run/memcached: -rw-r--r-- 1 memcache memcache 6 Apr 3 13:24 memcached.pid Both files contain the same PID but the latter one contains a newline too. A new stop/start will create new pid files. No warnings anymore. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
