Postgres Pro
Downloads
Home   >   mailing lists

Re: ipc-daemon2 failure - Mailing list pgsql-cygwin

From Roger Ackroyd
Subject Re: ipc-daemon2 failure
Date
Msg-id 006001c351d0$5d4eab30$b200a8c0@mydomain.com
Whole thread Raw
In response to ipc-daemon2 failure  ("Marvin" <magosoft@gmx.net>)
Responses Re: ipc-daemon2 failure
List pgsql-cygwin
Tree view
Marvin
 
Note the earlier post by Jason re: using cygwin 2.
 
With reference to cygwin1 -
Check the version on your cygwin1.dll in .../cygwin/bin. I had similar problems and found I was running something like 1.3.10. Upgrading to cygwin1.dll version 1.5.1. from http://cygwin.com/snapshots cleared the problems. Unzip it with bunzip2.
 
(Jason: I thought I had posted my solution last week as you requested. Probably never received due to my ineptitude at posting to lists. The above is essentially what I did in order to solve the issue on this XP Home machine.  On the readme, under requirements, it recommends cygwin 1.3.16-1. At footnote [16] ref step 10, it states 'For cygwin 1.3.22-1 and below, a bug prevents this from working...'. Is this problem something related to this without perhaps being the direct cause?)
 
Roger 
 
----- Original Message -----
From: Marvin
Sent: Wednesday, July 23, 2003 11:35 PM
Subject: [CYGWIN] ipc-daemon2 failure

I have just installed (at last) the CygWin on my XP Machine
I have followed every step, but when I try to start the ipc-daemon2:
 
$ ipc-daemon2 --install-as-service
 
as a NT Service I get the following error box:
 
"The procedure entry point __getreent could not be located in the dynamic link library cygwin1.dll"
 
 
I have a headache at this point.
Please help me.
I'm about to drop all this stuff.
 
Thank you for ANY ideas and comments.
 
 
MAGO
 
 
_________________________________________________________________
  IncrediMail - El E-mail ha evolucionado finalmente - Haga clic aquí
Attachment

pgsql-cygwin by date:

Previous
From: Jason Tishler
Date:
Subject: Re: INITDB problem
Next
From: Jason Tishler
Date:
Subject: Re: ipc-daemon2 failure