Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 194868

Summary: net-misc/memcached init -> multi (conf.d, init script included)
Product: Gentoo Linux Reporter: Walter <walter>
Component: New packagesAssignee: Robin Johnson <robbat2>
Status: RESOLVED FIXED    
Severity: enhancement CC: m.debruijne, robbat2
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: new init script - /etc/init.d/memcached

Description Walter 2007-10-06 00:21:38 UTC
memcache didn't support multi-service.

Attached is a new memcache init script.

New services read from /etc/conf.d/memcached.servicename -- old memcached config files will work out of the box, but PIDFILE is now ignored (it is generated based on the service name).

Reproducible: Always

Steps to Reproduce:
1.emerge memcache
2.notice it doesn't work multi

Actual Results:  
no multi

Expected Results:  
multi
Comment 1 Walter 2007-10-06 00:23:01 UTC
Created attachment 132692 [details]
new init script - /etc/init.d/memcached
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-11-26 22:27:56 UTC
> CONFDIR="/etc/openvpn"

Hmmm... Reopen with a unified diff against current ebuild, with all the relics of other ebuilds removed.
Comment 3 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2007-11-26 23:50:00 UTC
php: I'm taking memcached per lisa's original retirement mail.
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2007-11-26 23:53:34 UTC
Have phun... :) Not that I'd understand what's this bug about...

<snip>
elog "With this version of Memcached Gentoo now supports multiple instances."
elog "To enable this you must create a symlink in /etc/init.d/ for each instance"
elog "to /etc/init.d/memcached and create the matching conf files in /etc/conf.d/"
elog "Please see Gentoo bug #122246 for more info"
</snip>
Comment 5 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2007-11-27 01:27:09 UTC
1.2.4_rc1 is in the tree with this.
Please note that multiconf did work before, but you had the change the pidfile suitably (esp if you were listening on two addresses but the same port with different instances). I took the best of both worlds, and made the user specify just the prefix for the pidfile, and then append $PORT and ${CONF} to it to form the unique pidfile.