Hi Jason! Why not query_server.log ? However, this command is also available for externals and os_daemons, so probably even this name may be confused.
-- ,,,^..^,,, On Tue, Feb 5, 2013 at 3:38 PM, Jason Smith <[email protected]> wrote: > It used to be called "js_file" however it is properly the result of the > ["log", "..."] command from the view server. > > How about "views_log_file"? > > > > On Tue, Feb 5, 2013 at 11:13 AM, Robert Newson <[email protected]> wrote: > >> "view_file" is an awkward name, won't output from shows, lists, etc, >> also land here? >> >> On 5 February 2013 10:15, Jason Smith <[email protected]> wrote: >> > I want to merge this: >> https://github.com/apache/couchdb/commits/console_log >> > >> > Please comment if you have a moment. It is two changes. >> > >> > ## console.log() >> > >> > In addition to good old log(), there is console.log(). It behaves exactly >> > like Node.js. It supports a format string and variable arguments. >> > >> > console.log("doc id is %s and count is %d", doc._id, doc.count) >> > console.dir("doc = %j", doc) // JSON format >> > console.log("Full request\n%s", util.inspect(req)) >> > return { >> > body: util.format("<title>%s</title", title) >> > } >> > // etc. >> > >> > ## Separate log file for JavaScript >> > >> > _config/log/view_file = "js.log" >> > >> > If this is set, every log() or console.log() will additionally go to this >> > file. There are no timestamps, no formatting. It is like a console. >> > >> > I was thinking of adding /_log support, cleaning it up, and then merging >> it >> > in. >> > > > > -- > Iris Couch
