atom feed3 messages in com.googlegroups.memcachedIssue 201 in memcached: Defining a ch...
FromSent OnAttachments
memc...@googlecode.comApr 14, 2011 12:58 pm 
memc...@googlecode.comApr 14, 2011 1:03 pm 
memc...@googlecode.comApr 14, 2011 10:13 pm 
Subject:Issue 201 in memcached: Defining a chunk_size in a deamonized environment results in service start failure
From:memc...@googlecode.com (memc@googlecode.com)
Date:Apr 14, 2011 12:58:29 pm
List:com.googlegroups.memcached

Status: New Owner: ---- Labels: Type-Defect Priority-Medium

New issue 201 by ad.@yqed.com: Defining a chunk_size in a deamonized environment results in service start failure http://code.google.com/p/memcached/issues/detail?id=201

What steps will reproduce the problem? 1. Starting memcached daemonized with a defined chunk_size fails: daemon /usr/bin/memcached -d -l 127.0.0.1 -p 11211 -U 11211 -u memcached -P /var/run/memcached/memcached.pid -t 4 -m 64 -c 1024 -s 48 -f 1.25

What is the expected output? What do you see instead? Service dead but with subsys locked.

What version of the product are you using? On what operating system? 1.4.5, CentOS 5.6. 64bits

Please provide any additional information below. As soon as I remove the -s 48 condition, everything works as expected.