On Apr 23, 11:00 am, Benjamin Connelly <[email protected]> wrote: > We have occasionally seen our / partition overflow because memcached core > dumped. We're running FreeBSD and so memcached is launched on boot from > /usr/local/etc/rc.d/memcached.sh. Is there a way to have core files land > somewhere else?
You have more serious problems than where memcached dumps core: 1) The OS will typically dump a process' core in its working directory. memcached's working directory is /. If memcached can write to /, you're doing something really wrong (either running it as root or you have a writable root directory). Either way, that's a pretty nasty security problem. 2) memcached shouldn't dump core. Worry less about *where* it dumps core, and help us find out *why* it's dumping core for you. That just should not happen ever.
