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 dansantner@me.com designates
 17.158.232.236 as permitted sender)
Content-type: text/plain; charset=windows-1252
MIME-version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: is it safe to delete the log file?
From: Dan Santner <dansantner@me.com>
In-reply-to: 
 <CABvT1DGSGhhQ-H3D=BYKxzY9us=9TU2ojxTUXi-ZO2K5VaHNxA@mail.gmail.com>
Date: Wed, 31 Jul 2013 07:20:46 -0500
Content-transfer-encoding: quoted-printable
Message-id: <DEA0464C-A688-4222-BBE8-92A67DC1DFBB@me.com>
References: <5C8FCA89-17DE-4C05-A54F-FD87AE9A6FB7@me.com>
 <596F855F-8BED-44B0-B946-E1CEDF90E424@sri.com>
 <CABvT1DGSGhhQ-H3D=BYKxzY9us=9TU2ojxTUXi-ZO2K5VaHNxA@mail.gmail.com>
To: user@couchdb.apache.org

Thanks guys.  Glad I asked!  cat /dev/null did the trick.

On Jul 30, 2013, at 4:17 PM, Robert Newson <rnewson@apache.org> wrote:

> couchdb won't close the file descriptor, so be sure to use
> 'copytruncate' option with logrotate.
>=20
> B.
>=20
>=20
> On 30 July 2013 22:08, Jim Klo <jim.klo@sri.com> wrote:
>> when you built/installed couchdb=85 there should be a logrotated =
config file
>> that was generated somewhere that you either need to link or copy =
into
>> /etc/logrotate.d/couchdb:
>>=20
>> Here's the template file:
>> =
https://github.com/apache/couchdb/blob/master/etc/logrotate.d/couchdb.tpl.=
in
>>=20
>> you could probably just cut/paste and update the contents of this =
(which is
>> just the path to your couchdb log directory) straight into
>> /etc/logrotate.d/...
>>=20
>> also the safest way to truncate just about any log file is:
>>=20
>> sudo cat /dev/null > /path/to/your/logfile.log
>>=20
>> As it doesn't confuse any existing open file handles usually=85
>>=20
>> This is all assuming you are running on some Linux variant.
>>=20
>>=20
>> - JK
>>=20
>> Jim Klo
>> Senior Software Engineer
>> Center for Software Engineering
>> SRI International
>> t. @nsomnac
>>=20
>> On Jul 30, 2013, at 1:51 PM, Dan Santner <dansantner@me.com>
>> wrote:
>>=20
>> I know that sounds silly but....I've done that kind of thing before =
and
>> really regretted it afterwards.  So I'm asking you all.  Can I simply =
whack
>> the couch.log file and trust that couch will handle that gracefully?
>>=20
>> I've been using the same couchdb process for over a year now (maybe
>> restarted it like 4 times) locally and noticed my log file is over =
2G!
>>=20
>> Thanks,
>> Dan.
>>=20
>>=20