Re: postgres in freebsd jail

From: "Reko Turja" <reko(dot)turja(at)liukuma(dot)net>
To: "Bill Moran" <wmoran(at)potentialtech(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: postgres in freebsd jail
Date: 2004-08-17 07:01:35
Message-ID: 019601c48428$08c2a9f0$6987cb52@rekon
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

----- Original Message -----
From: "Bill Moran" <wmoran(at)potentialtech(dot)com>

> 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 upshot is that, personally, I don't know. I have not yet had
> time to
> track down the problem.

I guess you have set the following variables according your needs in
your kernel config file and then recompiled your kernel?

options SYSVSHM
options SYSVSEM
options SYSVMSG
options SHMMAXPGS=65536
options SEMMNI=40
options SEMMNS=240
options SEMUME=40
options SEMMNU=120

I don't have a system running -CURRENT or 5.x at this moment, so I
can't check if there are new sysctl's or kernel variables introduced,
which control the SYSV - One possible thing to do would be grepping
the output of sysctl -a and checking for word jail. (I tried to find
the thread you mentioned, but only found one post from you, so I'm
sorry if I'm just repeating the obvious...)

-Reko

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-08-17 07:15:58 Re: Does a 'stable' deferred trigger execution order exist? -> answer: yes
Previous Message Frank van Vugt 2004-08-17 06:53:27 Re: Does a 'stable' deferred trigger execution order exist? -> answer: yes