From: | dx k9 <bitsandbytes88(at)hotmail(dot)com> |
---|---|
To: | posgres support <pgsql-admin(at)postgresql(dot)org> |
Subject: | initdb |
Date: | 2009-01-09 21:04:19 |
Message-ID: | COL120-W2636FE1432B0B370782413D1DD0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I recently initdb'd with pwfile to create a new instance. The command is below.
I use pam in my hba files as my METHOD to allow ldap users in, but I normally don't initialize with --pwfile(wish I wouldn't have). Using --pwfile seems to have disabled my ability to use LDAP. I also noticed the postgres user shows a MD5 hash in it's properties, which indicates to me it's also using LDAP. I don't remember -W having this affect. Also, when I add ldap users(new to the instance), I add a new login via pgadmin with out a password. That normally works fine, but not now. Is it a bug that initializing the db with --pwfile cause pam not to allow ldap communications or is that by design. Is there someway I can turn it on or get out of this mess with out re-initializing the db with out the --pwfile option? The only thing I can think of is to specifically use ldap in the hba file instead of pam and see if that works. I can get my new users to work by just adding the password, but then I'm not using LDAP, which is what I want.
As the postgres user on the local server.
/usr/local/pgsql.v835/bin/initdb --pwfile=/home/postgres/pgp -D /data/Linux.pgsql/serray5432 -E UTF8
Thanks for any insight,
~DjK
_________________________________________________________________
Windows Live™: Keep your life in sync.
http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t1_allup_howitworks_012009
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2009-01-09 21:08:00 | Re: ssl database connection problems... |
Previous Message | Carol Walter | 2009-01-09 20:47:54 | Re: ssl database connection problems... |