From: | Ian Barwick <barwick(at)gmail(dot)com> |
---|---|
To: | raj veluchamy <rajpgsql(at)yahoo(dot)co(dot)in> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: nmap not showing postgres |
Date: | 2004-07-18 23:19:50 |
Message-ID: | 1d581afe04071816191cf59b2e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 18 Jul 2004 15:30:01 +0200, Ian Barwick <barwick(at)gmail(dot)com> wrote:
> On Tue, 13 Jul 2004 05:53:36 +0100 (BST), raj veluchamy
> <rajpgsql(at)yahoo(dot)co(dot)in> wrote:
> > hello all,
> > i am running postgres in compiling postgres in OSCAR
> > cluster.
> > installation is done to /home/pgsql as i couldn't do
> > it at /var/lib.
> > while i nmap, the postgres is not shown, but when i
> > give createdb, this is working and i could work on
> > with the data base.
>
> I'm guessing you want to ascertain whether PostgreSQL is listening on
> a TCP/IP port? I'm not familiar with OSCAR so I don't know whether it
> has any impact on PostgreSQL operations. A command like "netstat -t"
> should show you what services are listening on what ports.
Forgot to add: by default PostgreSQL doesn't listen on a TCP/IP port;
you have to specify this when starting the server.
Ian Barwick
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2004-07-18 23:46:26 | Re: Fwd: Indexes and Tables: Growth and Treatment |
Previous Message | Scott Marlowe | 2004-07-18 22:35:56 | Re: Error trapping in pg/PGSQL |