Thank you for your replies. Is it OK for the daemon to listen on all IPs, instead of specifying one IP address? Is there any issues with that? Performance? Security? PORT=11211 USER=nobody MAXCONN=1024 CACHESIZE=1024 OPTIONS=""
daemon memcached -d -p $PORT -u $USER -m $CACHESIZE -c $MAXCONN -P /var/run/memcached.pid $OPTIONS Thank you! Yael goldberg -----Original Message----- From: Dirk-Willem van Gulik [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 6:29 AM To: Just Marc Cc: Yael Goldberg; [email protected] Subject: Re: memcache on multiple servers On May 6, 2008, at 8:44 PM, Just Marc wrote: > You're trying to connect to 192.168.100.180 while your memcached > only listens on localhost... no wonder it fails. Either always > connect to 127.0.0.1 or change the IP on which memcached listens. You propably want to be careful with that - as then adding non-local host's -- and then later using that as a template elsewhere gets you inconsistent hashing. I.e. best perhaps to use absolutely IPs from the same CIDR across the board. Given how many times this has bitten me - you'd almost wonder if it makes sense to allow the config to drive the hashing by some UUID which is configured or persistently (re-)gurgitated by memcached on startup. Dw -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
