From: pierce at hogranch.com (John R Pierce)
Date: Sat, 24 Sep 2011 00:49:25 -0700
Subject: [Pljava-dev] Strange error on linux but not on windows
In-Reply-To: 
 <CALtUeZZRXa1+fHHbHXadmsuX09sLC0eBa+s4hAFAMzX+S-mT1w@mail.gmail.com>
References: 
 <CALtUeZYVhb3aySBt1GVZay4D-wiUUDmsACOQ+2VFB-+RQnHbQg@mail.gmail.com>
	<x6pqiwvi4z.fsf@2ndquadrant.com>
	<CALtUeZbJLA3u77hL9O_not27uV19F68-yXSO1ZeZ2ThC0qex1g@mail.gmail.com>
	<CALtUeZZSNx7LdzQDBbji76Lo=KfPFtwH5tG9wUwtooMFnNUPKw@mail.gmail.com>
	<x68vpjuu3j.fsf@2ndquadrant.com>
	<CALtUeZZ5VEMHjgs9HTvGZZRrcbSxkdxG2NhHtiZUQ7BFDV9L4g@mail.gmail.com>
	<CALtUeZZRXa1+fHHbHXadmsuX09sLC0eBa+s4hAFAMzX+S-mT1w@mail.gmail.com>
Message-ID: <4E7D8B85.7080104@hogranch.com>

On 09/24/11 12:20 AM, Vorarlberger wrote:
> I wannted to track down details into this issue so ... I have tried 
> several ways to get pg_ctl run with root provileges. And I have also 
> tried to bypass the ports < 1024 issue with tools like privbind or 
> setcap. I had no success ... 

the first one is easy...

     su -l postgres -c "pg_ctl start -D ... "

There are no good reasons for running a database server daemon as root 
such that its ignoring file protection.

And, I fail to see why would you want to run postgres on a low port?

-- 
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast