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

Frank,

On Wed, Apr 30, 2003 at 07:08:46PM -0400, Frank Seesink wrote:
> Jason Tishler wrote:
> >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, I should have been more clear.  I meant getting "ipctest s" to
work when run under the postgres user account.

> >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...
>
>     Actually, 2nd comment:  I disagree with your analysis.  As
> mentioned in my original post, initdb works JUST FINE when run as the
> administrative account that Cygwin was installed from.

Understood.  This is why I suggested tracing and gdb, because I can't
understand why initdb fails for postgres but succeeds for another user.

Let's try another approach.  Please strace "ipctest s" when run under
the postgres:

    $ strace -o ipctest.log ipctest s

and post ipctest.log to the list.  Remember to start ipc-daemon before
running the strace.

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