Yes, but don't. Why would you do that? On 8 Jan 2010, at 17:03, Zachary Zolton wrote:
> Okay, looking into my /usr/local/etc/default/couchdb file, I noticed > it contains the following: > > export COUCHDB_USER=couchdb > export COUCHDB_STDOUT_FILE=/usr/local/var/log/couchdb/couchdb.stdout > export COUCHDB_STDERR_FILE=/usr/local/var/log/couchdb/couchdb.stderr > > So, my question is can I just set those two file paths to /dev/null > without causing any problems? > > P.S. I'm using Monit to start CouchDB with: "/etc/init.d/couchdb > start", so it should be a standard daemon... > > On Thu, Jan 7, 2010 at 8:07 PM, Noah Slater <[email protected]> wrote: >> If you run CouchDB from the init script it will log to a standard log file >> under PREFIX/var/log, but if you run it manually from the command line, it >> will output to couchdb.stdout/stderr. It is up to you which you want to use, >> and what you do with the output in each case. I would advise using the init >> script where you are running it regularly as a daemon. >> >> On 7 Jan 2010, at 19:47, Matt Goodall wrote: >> >>> 2010/1/7 Zachary Zolton <[email protected]> >>> >>>> Relaxers, >>>> >>>> It seems the contents of my server's couch.log file and couchdb.stdout >>>> file are fairly identical, showing all the request being made to the >>>> server. >>>> >>>> Given the seeming redundant data, I ask: Do I need to maintain both >>>> these files? Or should I just add couchdb.stdout to my log rotation >>>> and forget about it? >>>> >>>> (I wasn't able to find any reference to this in the wiki, nor much >>>> useful information via Google.) >>>> >>>> >>>> Cheers, >>>> >>>> Zach >>>> >>>> >>>> P.S. I'm mostly interested in this since I was just bitten by a >>>> server's disk partition getting filled up by this very file... (^_-) >>>> >>> >>> Heh, I experienced something similar the other day. I run couchdb under >>> daemon and let daemon handle sending the couchdb output to a log file. A was >>> surprised to discover that couchdb was logging to var/log/couchdb/couch.log >>> too. >>> >>> Perhaps couchdb log to stdout when run in the foreground or couch.log when >>> daemonised? >>> >>> - Matt >> >>
