From: | Lacey Powers <lacey(dot)powers(at)commandprompt(dot)com> |
---|---|
To: | Scott Holmes <scott(dot)holmes(at)AMBERReady(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: newbie Administrator |
Date: | 2009-07-24 00:25:43 |
Message-ID: | 4A68FF87.8000806@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello Scott,
Hm. Having no pg_hba.conf file definitely sounds odd.
I'd try this command while logged in via psql:
SHOW hba_file;
The output should show you the path to the pg_hba.conf file, which you
can then edit to limit the connections to the database.
Hope that helps. =)
Lacey
>
> I have recently inherited a Linux server running pgsql and need to
> lock someone out but have so far been unsuccessful.
>
>
>
> I have changed the Linux passwords
>
> I have changed the passwords on the 3 users listed on the Database
>
>
>
> Now the problem is the person (server) I need to block access can
> still connect to the database. I have verified this by changing a
> record in the database and the changes were reflected on the other
> server. I looked for pg_hba.conf and there isn't one that I can find
> so I am wondering if it is a persistent connection and if it is how do
> I kill it? Will restarting the server drop the connection
>
--
Lacey Powers
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 ext 104
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Julius Tuskenis | 2009-07-24 07:07:13 | Re: Cannot connect to postgresql |
Previous Message | Joshua D. Drake | 2009-07-24 00:12:53 | Re: newbie Administrator |