| From: | "Joshua D(dot) Drake" <jd(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:12:53 |
| Message-ID: | 1248394373.1394.26.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2009-07-23 at 19:30 -0400, Scott Holmes wrote:
> 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
Yes restarting the database will drop the connection.
I guarantee you, you have a pg_hba.conf somewhere.
Joshua D. Drake
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lacey Powers | 2009-07-24 00:25:43 | Re: newbie Administrator |
| Previous Message | Scott Holmes | 2009-07-23 23:30:24 | newbie Administrator |