From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, postgresql(at)fruru(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgresql 7.2b5 and vserver: statistics sockets |
Date: | 2002-01-24 08:52:29 |
Message-ID: | 3.0.5.32.20020124165229.00f1e6b0@192.228.128.13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 12:08 PM 23-01-2002 -0500, Tom Lane wrote:
><postgresql(at)fruru(dot)com> writes:
>> If more people encounter the same problem (it's the way vserver works,
>> there are some good arguments on why not to make 127.0.0.1 available)
>
>Uh ... what are they? We're willing to listen to reasonable arguments
>why that needs to be configurable.
Just like to point out that if IP forwarding is enabled on a target host,
other hosts on the same network could access 127.0.0.1 on that target host
(or any interface for that matter).
For some target operating systems that may still work even if IP forwarding
is off.
e.g. use certain source operating systems, bring down 127.x.x.x if present,
add the route to 127.0.0.1 using gateway = target host adjacent IP. Now
ping or telnet 127.0.0.1.
Cheerio,
Link.
From | Date | Subject | |
---|---|---|---|
Next Message | Denis Perchine | 2002-01-24 09:14:11 | Problem with btree index on 7.1.3 |
Previous Message | Dmitry Alyabyev | 2002-01-24 08:19:26 | Re: Not Finding password for Postgres user on linux |