how to truncate the logs without kill memcached

Sheldon Chen schen at
Mon Oct 22 21:47:43 UTC 2007

thanks for the quick response.  that's what I figured.  I should have
used 2>>memcached.log.
we preload memcached with large amount of data and I just wanted to see
how it goes...


-----Original Message-----
From: Steven Grimm [mailto:sgrimm at] 
Sent: Monday, October 22, 2007 2:15 PM
To: Sheldon Chen
Cc: memcached at
Subject: Re: how to truncate the logs without kill memcached

No, and that's nothing to do with memcached; it's true of any program
where you're redirecting the output directly into a file.

Try piping output to some helper program that opens a new logfile every
so often. There are several such available (cronolog springs to mind).

Running with -vv in any kind of production environment is unusual. What
do you use all that information for, out of curiosity?


Sheldon Chen wrote:
> I have used memcached -d -m 1024 -vv 2>memcached.log to start the 
> memcached and found that the log file memcached.log grows too fast.  
> Is there a way to remove the logs without killing the memcached first?
> thanks,
> sheldon

More information about the memcached mailing list