Re: Fresh Installation of 7.1.1 RPMs = no binding to a port - Mailing list pgsql-general

From Lamar Owen
Subject Re: Fresh Installation of 7.1.1 RPMs = no binding to a port
Date
Msg-id 01052911101500.00912@lowen.wgcr.org
Whole thread Raw
In response to Re: Fresh Installation of 7.1.1 RPMs = no binding to a port  (Jorge Sarmiento <jsarmiento@ccom.org>)
Responses Re: Fresh Installation of 7.1.1 RPMs = no binding to a port  (teg@redhat.com (Trond Eivind Glomsrød))
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 28 May 2001 10:25, Jorge Sarmiento wrote:
> This is true, in Red Hat 7.1 with PostgreSQL RPMS 7.1.1 you have to
> MANUALLY edit the /etc/rc.d/init.d/postgresql and change the line:

> su -l postgres -c "LC_ALL=C /usr/bin/pg_ctl  -D $PGDATA -p
> /usr/bin/postmaster start >/dev/null 2>&1" < /dev/null

Please edit /var/lib/pgsql/data/postgresql.conf instead. This is documented
in the README.rpm-dist shipped with the RPMs.  If the documentation in the
README is insufficient, please let me know where I need to correct and
improve it.  But editing the initscript is not necessary -- and, in fact,the
next time you upgrade your RPM installation, your careful edits will be
overwritten as the newer initscript is put into place....

To find the README, execute the following:
rpm -ql postgresql | grep rpm

I have considered making the default back to TCP/IP listening -- but I am
inclined not to do so for security's sake (if postmaster isn't listening it
can't be portscanned) -- and, besides, on a from-source install the default
is to not listen over TCP/IP.

Again, this behavior is documented in the friendly README.rpm-dist shipped in
the main postgresql rpm.
- --
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7E7va5kGGI8vV9eERAk3hAJ9B+nVRUb8v5btUUxKwpdbPllxsiwCguG2u
OsLdnEoQcQgTlZSLQYdQhlU=
=2jRy
-----END PGP SIGNATURE-----

pgsql-general by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: 7.1.2
Next
From: Tom Lane
Date:
Subject: Re: Re: [SQL] Difficult SQL Statement