[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] GNUmed problem in Ubuntu 2
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] GNUmed problem in Ubuntu 2 |
Date: |
Wed, 13 Apr 2011 11:36:41 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Apr 13, 2011 at 01:31:30AM -0700, Jim Busser wrote:
> > For that you'll have to change two things:
> >
> > 1) on the database computer
> >
> > - allow access from other computers:
> > - add a line with "host" instead of "local" as the first token
> > to pg_hba.conf
> > - tell PostgreSQL to listen to other computers
> > - edit "listen_address" in postgresql.conf
> > -
> > http://wiki.gnumed.de/bin/view/Gnumed/ConfigurePostgreSQL#Permitting_access_to_the_databas
>
> At the above link are maybe some unclear things needing fixing? When it says
>
> "The changes must be made in postgresql.conf."
>
> the above is referring only to
>
> "Set the listen_address parameter to whichever network interfaces you
> want your GNUmed database to be available on. This is necessary in particular
> if you want to connect to your server from other machines."
>
> whereas should this instruction:
>
> You will then also have to add access permissions for those other
> machines in pg_hba.conf. Let's assume the remote machine sits behind the
> IP192.168.1.10:
>
> # IPv4 remote connections:
> host samegroup +gm-logins md5
>
> ... be relocated up into pg_hba.conf section of the wiki topic so that the
> results looks like this, with both lines required... or does one drop the
> line that begins "local"?
>
> # IPv4 remote connections:
> host samegroup +gm-logins md5
> local samegroup +gm-logins md5
I have updated the page to be more specific.
Can you check whether that's any better in terms of explanation ?
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346