Comment #1 on issue 154 by trond.norbye: pid file out of sync (created before socket binding)
http://code.google.com/p/memcached/issues/detail?id=154
I'm not sure if this bug actually makes any sense.. Given your error scenario you might expect the memcached to bail out before trying to write to the pid file, but that is just one of the alternatives. What if you had specified different port numbers or another ip address to bind to. What would the content of the pid be in those situations? all of the pids?
We could move the creation of the pid file to after we've allocated all resources and ready to start accepting clients, but the pid file would be just as ambiguous. I don't think we should add logic to memcached to read the pid file and refuse to start if the pid in there is already running (because then we would also have to check that we can connect to that host and getting the stats there to see if the pid is the same because that pid could be recycled etc)...
I vote for closing this bug as "invalid".
