This was fixed upstream in version 1.4.9, marking fix released.
** Changed in: memcached (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681090
Title:
** Changed in: memcached (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681090
Title:
status operation on init.d not working correctly
To manage notificat
** Changed in: memcached (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681090
Title:
status operation on init.d not working correctly
To manage notifications
Hi Clint,
no problem on making Ubuntu better, I owe it a lot.
I actually make a different init.d script for each memcache daemon.
This is handy in making a production level web app that leverages
memcache as I can have staging environments on 1 server. For example, I
have my production server li
Hi rynop, thanks for taking the time to file this bug report and help us
make Ubuntu better.
I have forwarded this to Debian and marked the bug report Triaged, with
an importance of Low.
One thing that has me confused is how exactly you intend to run "two
memcached concurrently" using just the in
--
status operation on init.d not working correctly
https://bugs.launchpad.net/bugs/681090
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
