Skip site navigation (1) Skip section navigation (2)

Re: installation problems

From: pgsql(at)mohawksoft(dot)com
To: jason(at)tishler(dot)net
Cc: pgsql(at)mohawksoft(dot)com, Ed(dot)Redman(at)dal(dot)ca,pgsql-cygwin(at)postgresql(dot)org
Subject: Re: installation problems
Date: 2003-04-28 14:39:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-cygwin
> On Fri, Apr 25, 2003 at 03:32:56PM -0400, pgsql(at)mohawksoft(dot)com wrote:
>> Funny, but cygwin's "symlink" mechanism is pretty poor.
> Huh?  AFAICT, Cygwin's symlinks work as expected (i.e., identical to
> symlinks on other Unixes).  Of course, Cygwin symlinks only work when
> interpreted by a Cygwin as opposed to Win32 process.

From the perspective of a Windows application trying to run a cygwin
application which is a symlink to another cygwin application it does not
look like UNIX symlinks.

Cygwin symlinks are *not* symlinks, they are application level indirections.
NT does support symlinks at the driver level, but I don't know if it is
practical or possible to use them for the file system.

>> Rather than using a symlink, copy postgres.exe to postmaster.exe and
>> see if that works.
> The above is unlikely to help.

Really? It is one of the things I needed to do to get the "PostgreSQL for
Windows" Install CD to work. 

It depends on which API is being used to load the executable. If the Windows
API is used to load the EXE, then you can not use a cygwin symlink.

In response to


pgsql-cygwin by date

Next:From: Jason TishlerDate: 2003-04-28 16:11:50
Subject: Re: Compiling cvs code with Cygwin problems
Previous:From: Jason TishlerDate: 2003-04-28 13:20:51
Subject: Re: A couple XP Postgres Cygwin problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group