Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 03 Aug 2003 19:19:16 -0400
From: Seth Rubin <srubin AT thoughtprocess DOT com>
Subject: RE: bug in setup.exe for postgresql-7.3.4-1
In-reply-to: <00c501c35923$87dfbba0$4661883e@starfruit>
To: Max Bowsher <maxb AT ukf DOT net>, cygwin AT cygwin DOT com
Message-id: <CNELLBDHOKALJPHOOBBEIELDDHAA.srubin@thoughtprocess.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal


The cygwin setup installed postgres.exe with 700 bits, not 755 mode bits.
The tarball has 755 bits set.  An extract from the tarball, with -xvf or
xpvf extracts in mode 755.

Myself (and Jason) are thinking there's an issue with the cygwin setup.
Maybe I'm being naive, but all this seems is an issue with chmod and/or copy
not being done properly on the postgres.exe file during installation.  I
don't see where ACL's or ntsec enters into it.

-- Seth

-----Original Message-----
From: Max Bowsher [mailto:maxb AT ukf DOT net]
Sent: Saturday, August 02, 2003 2:26 PM
To: Seth Rubin; cygwin AT cygwin DOT com
Subject: Re: bug in setup.exe for postgresql-7.3.4-1


Seth Rubin wrote:
> Jason suggested I forward this
>
> -- Seth Rubin
>    ThoughtProcess Techology LLC
>
> -----Original Message-----
> From: pgsql-cygwin-owner AT postgresql DOT org
> [mailto:pgsql-cygwin-owner AT postgresql DOT org]On Behalf Of Jason Tishler
> Sent: Saturday, August 02, 2003 10:46 AM
> To: Seth Rubin
> Cc: Pgsql-Cygwin
> Subject: Re: [CYGWIN] Updated Cygwin Package: postgresql-7.3.4-1
>
>
> Seth,
>
> On Fri, Aug 01, 2003 at 11:38:25PM -0400, Seth Rubin wrote:
>> postgresql-7.3.4-1 did not work immediately after I upgraded on my XP
>> Home system, but it's OK now.  It was fairly simple -- Here's
>> basically what happened:
>>
>> 1) upgraded my cygwin, including postgresql, from
>> ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
>> 2) did 'net start postmaster'    (I have postgres set up as NT service)
>>    It failed.  Found this in /var/log/postmaster.log:
>>
>>      LOG:  FindExec: invalid binary "/usr/bin/postgres"
>>      FATAL:  /usr/bin/postmaster: could not locate executable, bailing
>> out...
>>
>> 3) Looked at postgres.exe.
>>
>>     $ ls -l /usr/bin/postgre*
>>     -rwxr-x---+   1 Owner    Users     1985024 Aug  1 16:02
>> /usr/bin/postgres.exe
>
> The permissions of postgres.exe is correct in the tarball:
>
>     $ tar -tvjf postgresql-7.3.4-1.tar.bz2 usr/bin/postgres.exe
>     -rwxr-xr-x jt/Domain Users 1985024 2003-08-01 16:02:43
> usr/bin/postgres.exe
>
> AFAICT, the above problem is due to a bug in Cygwin's setup.exe.  Please
> report the problem to the Cygwin list.

Not a bug, so much as the inevitability of being unable to fully represent
all ACLs in POSIX mode bits.

Ultimately, it comes down to a simple choice: Turn off ntsec, or plan your
ACLs carefully.

Max.


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