Re: [Gnumed-devel] Re: Updated server packages

[Karsten Hilbert]

On Mon, Sep 21, 2009 at 11:43:58PM +0200, Christian A. Reiter wrote:

> > > > or by just telling the user that he should do this if run
> > > > as other user.
> > > 
> > > A good suggestion. I will add some code to the bootstrapper
> > > which warns about the line missing in pg_hba.conf.
> > 
> > I'd consider this as a very sane compromise which comes quite cheap.
> 
> I saw the line you wrote - It's good, but not perfect :-)
> Just the line is again not enough, it has to be on the right place as well.
> Honestly, what I would do is write something like:
> 
> "The postgresql server finally has to be configured to run with Gnumed, 
> please look at http://wiki.gnumed.de/bin/view/Gnumed/ConfigurePostgreSQL to 
> see how."
> 
> aut idem ;-)
> 
> Then you have as well the flexibility to change things on the Homepage or 
> give additional hints...

1st Law Of Software Development

        Thou Shalt Consider Listening To Thy Users.


==> sanity checking PostgreSQL authentication settings ...

Note that even after successfully bootstrapping the GNUmed
database PostgreSQL may still need to be configured to
allow GNUmed clients to connect to it.

In many standard PostgreSQL installations this amounts to
adding the authentication directive:

  "local   samegroup   +gm-logins   md5"

in the proper place of the file:

  /etc/postgresql/8.4/main/pg_hba.conf

For details refer to the GNUmed documentation at:

  http://wiki.gnumed.de/bin/view/Gnumed/ConfigurePostgreSQL

Done bootstrapping GNUmed database: We very likely succeeded.



Caveat:

1) the PostgreSQL server you just bootstrapped your database
   in is asked for the path of the pg_hba.conf file

2) the above message is only displayed if

        a) the server can tell us the pg_hba.conf path and
        b) that file does not contain the line (w/ or w/o md5) *at all*

This does not (and cannot, sanely) determine whether the
line is in the proper place. It also assumes (perhaps
unduly) that users associate connection problems with a
potential need to configure connectivity...   ;-)

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346