search

cumulus13 / memcached

Automatically exported from code.google.com/p/memcached
0 stars 0 forks source link

Memcached cannot be controlled by start-stop-daemon #396

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install memcached
2. Call scripts/memcached-init start
3. Call scripts/memcached-init status

What is the expected output? What do you see instead?
* Expect to see "Memcached is running", see "Memcached is not running/stopped"

What version of the product are you using? On what operating system?
* Version 1.6 (trunk) on Ubuntu 12.04.

Please provide any additional information below.
* The issue is that the pidfile is populated with the pid of one of the forks 
that start-memcached uses to drop TTY connections rather than the PID of the 
final memcached process.
* If the memcached is configured to daemonize, this causes even more issues (as 
the pidfile is invalidated again) but that can easily be turned off in 
/etc/memcached_*.

Original issue reported on code.google.com by andy.m.c...@gmail.com on 20 Feb 2015 at 5:16

GoogleCodeExporter commented 9 years ago 
I think https://github.com/memcached/memcached/pull/103 is the right fix 
(causes start-memcached to save off the pid that calls exec).

Original comment by andy.m.c...@gmail.com on 20 Feb 2015 at 5:18