On Tue, Sep 27, 2005 at 10:25:03PM +1000, Craig Small wrote: > Then again.... > If Postgres is setup like this then when whoever wants to access it, > they will need to have a unix user (even if it is www-data) so they sort > of need to get the user sorted out anyhow.
the real question is whether the application is designed to run with
its own system user, or whether the user it runs as is irrelevant and
a set of user/pass credentials are needed. in the former, the package
should have already installed such user and this authentication method
would work. in the latter, we shouldn't even be trying this method.
you (the package maintainer) can already hint to dbconfig-common the
connection method and username by setting the values before calling
dbc_go (there's some info on this in the html docs, iirc). however,
as i mentioned previously i'm working on making dbconfig-common a little
more intelligent about this.
> More digging has given me some interesting results. I'm not a shell
> guru so i don't understand why this happens.
> I have an evil fix, you might not like it but I can install and purge
> the db-test-pgsql package with it.
>
> Have a variable in the dpkg/* files that saves the database name.
> Use that each time to set the dbc_dbname variable.
thanks for the extra digging. if i can't root out the problem by this
weekend, i'll use your suggestion as a temporary fix while i investigate
where the hell this is happening.
sean
--
signature.asc
Description: Digital signature
