couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noah Slater (JIRA)" <>
Subject [jira] Commented: (COUCHDB-278) bin/couchdb does not honour -o and -e when running in foreground / without -d (matters on macosx)
Date Wed, 04 Mar 2009 10:25:58 GMT


Noah Slater commented on COUCHDB-278:

The -o and -e options are only provided so that that the -b option can redirect output, I
do not want to provide a generic way to redirect output. In fact, I'm not sure why this command
would want to produce output in the first place, that's what the log file should be used for.
If you think that the output to STDOUT and STDERR is too verbose, or that it should be sent
to the log file only, please open another bug for that. Note that using init.d redirects these
to /dev/null anyway, so I think there should be a little information sent over STDOUT and
STDERR as possible.

> bin/couchdb does not honour -o and -e when running in foreground / without -d (matters
on macosx)
> -------------------------------------------------------------------------------------------------
>                 Key: COUCHDB-278
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System, Database Core
>         Environment: any *nix
>            Reporter: Florian Ebeling
>             Fix For: 0.8.1, 0.9
>         Attachments: COUCHDB-278.diff
> When couchdb is running in foreground, then the option flags -o and -e are not honoured.
This probably quite ok on most systems because foregroud there equals roughly to development
mode. On the mac this is different, because fork and daemoinze calls are deprecated, services
are managed using launchd, and launchd watches these processes directly. It depends on these
processes not (double-)forking and intentionally dying.
> So in the current state of things the provided plist starts couchdb, quite consequentially
does not use -o/e and. That works, but has the effect that couchdb writes to stdout, which
launchd apparently forwards to syslog. So the syslog ends up being hogged by access-log level
messages. And it is not possible to avoid that by simply editing the quasi config file .plist.
> I will attach a patch which changes bin/couchdb, .plist, and etc/ to make
this work more like I reckon it should.

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

View raw message