couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-412) CouchDB fails to start when log file is a pipe
Date Fri, 07 Aug 2009 13:50:14 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740555#action_12740555
] 

Adam Kocoloski commented on COUCHDB-412:
----------------------------------------

CouchDB executes the following code:

Filename = couch_config:get("log", "file", "couchdb.log"),
{ok, Fd} = file:open(Filename, [append]),

I tried using a pipe in a plain erl shell:

$ mkfifo -m 777 blah.log
$ ls -l blah.log
prwxrwxrwx  1 kocolosk  staff  0 Aug  7 09:45 blah.log

$ erl
Erlang R13B (erts-5.7.1) [source] [smp:2:2] [rq:2] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.7.1  (abort with ^G)
1> file:open("blah.log", [append]).
{error,eisdir}

Sure enough, in the Erlang manual for file:open there's a list of common error codes that
includes

eisdir:
             The  named  file  is not a regular file. It may be a directory, a
             fifo, or a device.

I'll do a little more digging to see how one is supposed to handle FIFOs in Erlang.

> CouchDB fails to start when log file is a pipe
> ----------------------------------------------
>
>                 Key: COUCHDB-412
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-412
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.9
>         Environment: CentOS x86_64
>            Reporter: Enda Farrell
>
> I have an 0.9 CouchDB. When the local.ini file's [log] file is actually a pipe (with
a known to be running consumer) rather than a file, CouchDB fails to start.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message