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

Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 /

From: Jason Tishler <jason(at)tishler(dot)net>
To: Frank Seesink <frank(at)mail(dot)wvnet(dot)edu>
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 /
Date: 2003-04-30 19:01:44
Message-ID: 20030430190144.GB1428@tishler.net (view raw or flat)
Thread:
Lists: pgsql-cygwin
Frank,

On Wed, Apr 30, 2003 at 12:55:40PM -0400, Frank Seesink wrote:
> And no matter what, the following test was always the same when run
> from the 'postgres' user account:
> ______________________________________________________________________
> $ ipctest s
> Test v0.03
> Unable to create semaphore
> semget : Function not implemented
> ______________________________________________________________________

The above is the crux of your problem.  Until you get the above to work,
PostgreSQL is sure to fail.  Sorry, but my only suggestion will require
some effort.  I recommend building a (debug-able) version of cygipc with
tracing enabled.  You may be able to determine what the problem is from
the trace output.  Otherwise, there is always gdb...

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

Responses

pgsql-cygwin by date

Next:From: Frank SeesinkDate: 2003-04-30 23:05:53
Subject: Re: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 /
Previous:From: Frank SeesinkDate: 2003-04-30 16:55:40
Subject: initdb failure with PostgreSQL 7.3.2 / Cygwin 1.3.22-1 / CypIPC 1.13.2-1 / Windows XP Pro

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