Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <00bb01c35a16$9057cf40$5400a8c0@starfruit> From: "Max Bowsher" To: "Seth Rubin" , References: Subject: Re: bug in setup.exe for postgresql-7.3.4-1 Date: Mon, 4 Aug 2003 00:25:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Seth Rubin wrote: > 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. Here's how: Cygwin setup *doesn't* chmod anything at all. Hence, the file permissions end up being set by normal Windows inheritance. Now, interpret that through ntsec, and you end up with mode 700 - on your particular system. Setup does try to help things to turn out right, by setting the group to Users, on the grounds that most systems will grant Users at least Read&Execute, and most users will be in group Users. That apparently doesn't hold true on your setup, hence your problems. 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/