couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ulises Cervino Beresi (JIRA)" <>
Subject [jira] Commented: (COUCHDB-153) Erlang should warn about log/data file permissions
Date Mon, 09 Feb 2009 08:46:59 GMT


Ulises Cervino Beresi commented on COUCHDB-153:

I'm happy to take on this.

As for your comments:

tabs -> spaces: yes, bloody erlang-mode, for some reason it refuses to use spaces instead
of tabs, my fault entirely, I thought I had fixed it.
?LOG_ERROR + io:format(): I wanted both immediate messaging as logging for future reference.
Somehow (and I could be wrong here) with a single ?LOG_ERROR you wouldn't get the message
on the console.
as for pretty return vs. stop(): stop() didn't seem to stop the whole boot process. My limited
knowledge prevented me from investigating further why stop() (what's actually intuitive) didn't
ugly message: yes, but that's at a higher level. Either we tackle this from a higher level
in do_boot (if at all possible as you suggest) or we live with the extra ugly message taking
comfort that at least the one before makes a bit more sense.

Either way, I'm on it.

> Erlang should warn about log/data file permissions
> --------------------------------------------------
>                 Key: COUCHDB-153
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Infrastructure
>            Reporter: Noah Slater
>            Assignee: Jan Lehnardt
>            Priority: Critical
>         Attachments: issue-153.patch
> CouchDB is installed as root for most people, and hence without remembering to change
the permissions on the log/data directories, errors are very common. The problems caused by
incorrect permissions can be very confusing. We should re-add the checks for these that used
to be in the init script, but place them in CouchDB core. We need to do this so that the multiple
configuration settings will be taken account for.

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

View raw message