Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of kevin.r.coombes@gmail.com
 designates 209.85.160.180 as permitted sender)
Message-ID: <4F05EF0F.8060804@gmail.com>
Date: Thu, 05 Jan 2012 12:42:23 -0600
From: "Kevin R. Coombes" <kevin.r.coombes@gmail.com>
Organization: UT M.D. Anderson Cancer Center
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Managing Couch Log File
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

In response to a separate thread about replication, Dave Cottlehuber 
asked to see the log file from a remote CouchDB from which I was trying 
to replicate.  I then sent a request to the person managing that 
machine.  In return, I received a text file that was about 500 MB.  
That's rather a long file to search through, and my text editor did not 
fare well. (I wrote a perl script to loop through and find the part of 
the log from the day I needed; that's not my question for today.)

My question is: how do people manage these log files?  Do you have some 
automated procedure for splitting pieces off to archive them for a 
while? Does couch provide admin tools to help with this? Or do you just 
let the logs grow to gargantuan sizes?

     Kevin