Re: PSQL Working, but PGAccess Not Connecting.

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: David Lloyd-Jones <david(dot)lloyd-jones(at)attcanada(dot)ca>
Cc: Red Pineseed <yue207(at)home(dot)com>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: PSQL Working, but PGAccess Not Connecting.
Date: 2000-07-31 04:53:26
Message-ID: 39850646.77AF69E@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

David Lloyd-Jones wrote:
>
> I did try the loopback, as I mentioned in a note to Tom (perhaps off-line,
> sorry.)
> Agreed, his explanation makes sense, and I'm looking for the right place to
> put the -i.
>
> Anybody know the innards of that /etc/rc.d/init.d/postgresql start
> batchfile?

The older RPMS started the postmaster without the -i for security
reasons. However, the newer ones do start it up with TCP/IP
support enabled by default. Which rpms are you using? You should
look for a line like:

su -l postgres -c '/usr/bin/postmaster -o -F -i -S
-D/var/lib/pgsql'

The -o -F flag combination turns off fsync. The -i switch will
enable the TCP/IP connection. -S says to start up in silent mode.
-D specifies the location of the where the data/base hierarchy is
stored. If I recall the older RPMS correctly, they will have a
line like:

su -l postgres -c '/usr/bin/postmaster -S -D/var/lib/pgsql'

So all you'll have to do is change it as it appears above with
the -i switch (and I also recommend the -o -F pair as well).

Hope that helps,

Mike Mascari

P.S.: If you are using the older RPMS with an older version of
PostgreSQL (6.x), I highly recommend upgrading. Major bugs fixes
and enhancements were made between the 6.x series and 7.x.

Good Luck!

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Grant Finnemore 2000-07-31 05:10:12 Re: Access and Postgres question.
Previous Message David Lloyd-Jones 2000-07-31 04:17:23 Re: PSQL Working, but PGAccess Not Connecting.