Message-ID: <4BE99840.7050903@dunslane.net>
Date: Tue, 11 May 2010 13:47:44 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: psql "setsid" error
References: <t2neb3a2d501004272327lc811e513ya395aa495e6445e@mail.gmail.com> <4BE99110.2080107@x-ray.at>
In-Reply-To: <4BE99110.2080107@x-ray.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


Reini Urban wrote:
> Gary . schrieb:
>> psql: FATAL:  setsid() failed:
>> Operation not permitted
>
> Hmm, known problem.
> I'll change it like
> sed --in-place -e's/#define HAVE_SETSID 1/#undef HAVE_SETSID/' \
>     src/include/pg_config.h
>

This is completely the wrong thing to do. pg_config.h is an 
autogenerated file. If anything, it should go in pg_config_manual.h, but 
much better would be to fix the configure check, if it's wrong. Just 
hacking the config files is a losing game.

Butr why does it fail anyway? It works just fine on the PostgreSQL 
Buildfarm. See 
<http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=brown_bat&dt=2010-05-09%20183006&stg=config>

cheers

andrew

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple