Summary: | Postgres ebuild fails to setup log file if it's not in the default place | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Luca Lesinigo <luckyluke> |
Component: | Current packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Luca Lesinigo
2005-05-08 12:24:33 UTC
Why is this a bug? The ebuild works, if you want to move postgresql log to somewhere else, then set the location _after_ you have run ebuild config and set the permissions as needed... Why shouldn't it be a bug, even if it's a small one? I thought that if there is the ebuild config stuff, and if it in the end says "OK, you're setup, run init.d/postgresql start, be happy", it should give me a consistent setup. If you want the user and not the ebuild to take care of a touch & chmod, then remove all the ebuild config stuff and tell him to RTFM and setup postgres himself. That will leave you in a consistent state, and not in an halfway one. If that's not possible, the "Success. You can now start the database server using blahblah" message is actually a bug because it's wrong, and it should be changed in something like "Success. Maybe you can now start the database server, but look around if you eventually have to do something else before". PS, the first thing you can setup in conf.d/postgresql is the database directory. And you need to do that *before* running the ebuild config. Same applies for $PGUSER. This works just fine by default; if you need another location, see comment #1 |