RE: Any experiencies of PG 7.0.2 on OS/2 Warp? - Mailing list pgsql-admin

I have no idea how it's done on Warp, but you need to enable semaphores so
that PostgreSQL can create one for its use.  I know on Solaris you edit the
/etc/system file, and I think it's automatic on Windows (I never tried
PostgreSQL on that platform so I don't know for sure), but have no clue on
how to enable them on Warp.  They may be enabled by default and the max
segment size is not large enough or something.  I know on Solaris I had to
up the size because I also run some other programs that use semaphores.

HTH,

Fred Reimer
Eclipsys Corporation

> -----Original Message-----
> From: pgsql-admin-owner@hub.org [mailto:pgsql-admin-owner@hub.org]On
> Behalf Of SchiSchi
> Sent: Friday, October 06, 2000 9:47 AM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] Any experiencies of PG 7.0.2 on OS/2 Warp?
>
>
> Hi,
>
> I'm using Warp V3 for windows (german edition), fixpack is 40
> (revision
> level 8.264). For TCP/IP access, I installed the Internet
> Access Kit (V
> 2.0) running with local loop (loopback done by running
> "ifconfig.exe lo
> 127.0.0.1 up"). The EMX level is 0.9d. Hardware is 486DX80, 36MB RAM.
>
> After installing, I'm able to run the POSTMASTER and also the creation
> of "template1" (using "initdb") works fine.
>
> As soon as I start the client, at first it crashes and
> immediately after
> that the server is pulled down also.
> The reason, I see is "Creation de Semaphore 'Sem' impossible".
> (POSTMASTER was started: "POSTMASTER.EXE -i")
>
> Here is the log from server:
> >**LOG starts**********
> >reset_client_encoding()..
> >reset_client_encoding() done.
> >postmaster.exe: reaping dead processes...
> >postmaster.exe: CleanupProc: pid 75 exited with status 11
> >Server process (pid 75) exited with status 11 at Wed Oct 04 12:06:30
> 2000
> >Terminating any active server processes...
> >Server processes were terminated at Wed Oct 04 12:06:30 2000
> >Reinitializing shared memory and semaphores
> >shmem_exit(0)
> >NOTICE:  IpcMemoryDetach: shmdt(0x0x14aa0000): Invalid argument
> >NOTICE:  IpcMemoryDetach: shmdt(0x0x146f0000): Invalid argument
> >NOTICE:  IpcMemoryDetach: shmdt(0x0x14ac0000): Invalid argument
> >binding ShmemCreate(key=52e325, size=1115136)
> >Creation de Semaphore "Sem" impossible
> >IpcSemaphoreCreate: semget failed (Not enough memory) key=5432115,
> num=16, permi
> >ssion=600
> >This type of error is usually caused by an improper
> >shared memory or System V IPC semaphore configuration.
> >**LOG ends**********
>
> The client I try to start, is the first client.
>
> Is there any other in the universe, having this or similar
> version level
> and no problems running Postgres? What configuration is needed running
> PG under Warp?
>
> Thanks for your answer.
> Holger
>
>
>