Oh, one more thing: please don't run memcached (or anything else where it isn't absolutely necessary) as root. This is very dangerous. That's why memcached refuses to do it unless you want forcefully tell it that it's wrong and that you know what you're doing and to hell with security issues.
We do, of course work hard to write clean, secure code, but bugs are possible, and security is best served in layers -- each of which doing the most it can to reduce attack vectors. I won't go as far as to say it's *always* wrong to run memcached as root, but feel free to take that out of context and pretend like I did. On Jul 14, 7:21 am, gunyhake <gunyh...@gmail.com> wrote: > @tom sorry, i got the wrong switch. > > @dustin I have run again without -d switch, here is the result > > [root]# memcached -u nobody -m 512 -l 127.0.0.1 -U 11222 > failed to listen > > [root]# memcached -u root -m 512 -l 127.0.0.1 -U 11222 > failed to listen > > Maybe I should ask my host to help me take a look at this as well > > On Jul 12, 1:35 am, Dustin <dsalli...@gmail.com> wrote: > > > > > On Jul 11, 2:38 am, gunyhake <gunyh...@gmail.com> wrote: > > > > I tried with -u option, here is the result > > > > # memcached -d -m 512 -l 127.0.0.1 -u 11222 > > > Again, try to run without daemonization to see more errors. If it > > doesn't tell you why it's failing, we need to fix that.
