From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | Reko Turja <reko(dot)turja(at)liukuma(dot)net>, vvikram(at)stanford(dot)edu, pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgres in freebsd jail |
Date: | 2004-08-16 14:15:39 |
Message-ID: | 20040816111433.H55723@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 16 Aug 2004, Bill Moran wrote:
> "Reko Turja" <reko(dot)turja(at)liukuma(dot)net> wrote:
>
>>> I am using postgresql 8.0beta in a freebsd jail environment. My
>>> inittdb
>>> gives me a message like:
>>> ---
>>> creating template1 database in /home/..../db/base/1 ... FATAL:
>>> could
>>> not create shared memory segment: Function not implemented
>>> DETAIL: Failed system call was shmget(key=1, size=1187840, 03600).
>>> child process exited with exit code 1
>>> initdb: failed
>>
>> Have you enabled jail.sysvipc_allowed sysctl for kernel? I haven't run
>> Postgresql in jail myself but as far as I know the sysctl above is
>> needed in order to use sysv IPC and shared memory functionality inside
>> the jail.
>
> I was unable to get Postgres working in a jail even with this sysctl
> enabled. If you look through the archives, you'll see a discussion with
> others who have it working just fine.
The database that runs pgfoundry.org/gborg.postgresql.org and
www.postgresql.org are in a jail ... so definitely know it works ... as to
the above error, my first thing to check would be as Reko mentioned, check
that ipc within jail is allowed ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2004-08-16 14:20:44 | Re: Thousands of parallel connections |
Previous Message | Thomas Hallgren | 2004-08-16 14:13:02 | Re: PostgreSQL 8.0 Feature List? |