[Expired for memcached (Ubuntu) because there has been no activity for
60 days.]
** Changed in: memcached (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to memcached in Ubuntu.
[Expired for memcached (Ubuntu) because there has been no activity for
60 days.]
** Changed in: memcached (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to memcached in Ubuntu.
Is there anything that can be done about this? Bug still affects me.
** Changed in: memcached (Ubuntu)
Status: Expired = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to memcached in Ubuntu.
How can we move forward on this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to memcached in Ubuntu.
https://bugs.launchpad.net/bugs/1176178
Title:
Setting pid in memcached.conf causes strange behavior
To manage notifications
It would appear as though the init script is creating the pid with
root:root ownership, irrespective of memcached.conf's contents, yet
still passes the -P during memecached's exec. When the -P option is
added to the config, it results in this error as memcached tries to
create a pid that already
Thanks for reporting this
Can you provide the configuration file for memcached, and describe us the
permissions for the /var/run folder?
** Changed in: memcached (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
$ ls -l /var/run
lrwxrwxrwx 1 root root 4 May 3 20:20 /var/run - /run
$ less /etc/memcached.conf
# memcached default config file
# 2003 - Jay Bonci jaybo...@debian.org
# This configuration file is read by the start-memcached script provided as
# part of the Debian GNU/Linux distribution.
#
