Re: Initdb fails... Again!

From: Jason Tishler <jason(at)tishler(dot)net>
To: Markko Paas <Markko(at)softronic(dot)ee>
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: Initdb fails... Again!
Date: 2003-01-20 18:46:08
Message-ID: 20030120184608.GA2088@tishler.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

Markko,

On Mon, Jan 20, 2003 at 07:35:37PM +0200, Markko Paas wrote:
> Well, I copied the snapshot.
> But I had a bit different directory tree ... I don't think that can
> cause any problem, but...
> I copied
> /usr/bin, /usr/etc, /usr/lib --> /cygwin
> /usr/include, /usr/info /usr/man --> /cygwin/usr (as it should be??)

Sorry, but I guess that I should have been more clear. I meant just
replace your cygwin1.dll with the latest snapshot -- not the entire
binary tree.

> Still the same result:
>
> $ uname -a
> CYGWIN_NT-5.0 pull 1.3.19s(0.71/3/2) 20030119 22:03:54 i686 unknown
>
> postgres(at)pull ~
> $ rm ipc-ver.txt
>
> postgres(at)pull ~
> $ ipc-daemon --version 2>ipc-ver.txt
>
> postgres(at)pull ~
> $ cat ipc-ver.txt
> 6 [unknown (0xF58)] ipc-daemon 3700
> fhandler_console::fixup_after_exec: er
> ror opening input console handle after exec, errno 13, Win32 error 5

Please take this problem to the Cygwin list <cygwin(at)cygwin(dot)com> because
I must be missing something. Also, I hope that the cygipc maintainer
will chime in too. My suggestion is to focus on the ipctest problem
instead of PostgreSQL. However, I think that it is OK to mention that
PostgreSQL is affected too.

Thanks,
Jason

--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6

In response to

Browse pgsql-cygwin by date

  From Date Subject
Next Message martin ruff 2003-01-20 19:40:07 RE # Upgrading to 7.3.1 problem
Previous Message Markko Paas 2003-01-20 17:35:37 Re: Initdb fails... Again!