[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] More info on segfaulting on startup.
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] More info on segfaulting on startup. |
Date: |
Mon, 25 Apr 2005 17:00:56 +0200 |
User-agent: |
Mutt/1.3.22.1i |
On Mon, Apr 25, 2005 at 10:42:20PM +0800, Syan Tan wrote:
> >> I was able to install the backend using the
> >> ../test-area/cygwin/install_schema.sh
> >> , but am still having difficulty with redo-max.sh
> it's my pg_hba.conf file.
> if make local connections for all databases by all users including postgres ,
> authorization method by md5 hashing of password,
> it works.
> Previously I had postgres user using "ident same user" for all databases,
> md5 for gnumed for all users, and ident same user for all databases ( hoping
> that the preceding declaration about gnumed would not be overwritten, which
> it probably was).
I see.
> It looks like if postgres , and all other users including gm-dbo has md5
> access to template1 and gnumed, then the script will work.
It likely would.
> If it's possible, perhaps have the script offer to write the correct
> pg_hba.conf
> file, if given the base directory of the postgres data ?
No way :-))
> Or better yet, try to get it to check the pg_hba.conf file so that it will
> classify why the script might not work, and inform the user,
Very good suggestion. I dearly hope someone finds time to
implement it.
> requesting
> to overwrite the pg_hba.conf file ( after shutting down the postgres
> database).
Again, no way ;-)
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346