Date: Wed, 19 Jun 2002 09:27:42 -0700 From: Joseph Maxwell <jemaxwell@jaymax.com> To: questions@FreeBSD.ORG Subject: Problems w/ Semaphore - I'm in 'jail' Message-ID: <3D10B0FD.F0B7F4A5@jaymax.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Hello,
Hope there are users in this group w/ PostgreSQL familiarity and this
BSD interaction
I am setting up postgreSQL and have ran into a problem related to either
kernel config or operating within 'the jail'.
Some interactions w/ the postgresql user groups ==>
Systems: PostgreSQL version 7.2.1, with all default settings on a
BSD platform ,4.5-RELEASE FreeBSD.
hostname# initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned
by user "postgres".
This user must also own the server process.
Fixing permissions on existing directory
/usr/local/pgsql/data... ok
creating directory /usr/local/pgsql/data/base... ok
creating directory /usr/local/pgsql/data/global... ok
creating directory /usr/local/pgsql/data/pg_xlog... ok
creating directory /usr/local/pgsql/data/pg_clog... ok
creating template1 database in
/usr/local/pgsql/data/base/1...
IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed:
Function not implemented
initdb failed.
Any ideas on the semget() function, remembered reading on it
somewhere before but
can't remember where
I hope this does not call for a kernel rebuild
I did an ipcs -s which ===>
hostname# ipcs -s
Semaphores:
T ID KEY MODE OWNER GROUP
hostname#
Any insight on this type of problem?
Response ===>
Hmm, usually this means either the kernel's not configured for SYSV
ipc
or that you're running in a jail and the sysctl to let the jail use
sysv ipc is not turned on.
Is this a plausible explanation, & if it is that the kernel's not
configured for SYSV ipc
or that I am running in a jail how can the sysctl be turned on to allow
the jail to use sysv ipc?
Thanks
I've spoken w/ my ISP, Tech. support personnel not quite familiar w/
problem but promised to investigate.
Any other experienced opinions welcomed ...
--- Joe ---
[-- Attachment #2 --]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hello,
<br>Hope there are users in this group w/ PostgreSQL familiarity and this
BSD interaction
<br>I am setting up postgreSQL and have ran into a problem related to either
<br>kernel config or operating within 'the jail'.
<p>Some interactions w/ the postgresql user groups ==>
<p>Systems: PostgreSQL version 7.2.1, with all default settings on
a
<br> BSD platform ,4.5-RELEASE FreeBSD.
<br>
<blockquote> hostname# initdb -D /usr/local/pgsql/data
<br> The files belonging to this database system will be owned
by user "postgres".
<br> This user must also own the server process.
<p> Fixing permissions on existing directory /usr/local/pgsql/data...
ok
<br> creating directory /usr/local/pgsql/data/base... ok
<br> creating directory /usr/local/pgsql/data/global... ok
<br> creating directory /usr/local/pgsql/data/pg_xlog... ok
<br> creating directory /usr/local/pgsql/data/pg_clog... ok
<br> creating template1 database in /usr/local/pgsql/data/base/1...
<br> IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed:
Function not implemented
<p> initdb failed.
<br> </blockquote>
Any ideas on the semget() function, remembered reading on
it somewhere before but
<br> can't remember where
<br> I hope this does not call for a kernel rebuild
<br> I did an ipcs -s which ===>
<br>
<blockquote> hostname# ipcs -s
<br> Semaphores:
<br> T ID
KEY MODE
OWNER GROUP
<p> hostname#
<br> </blockquote>
Any insight on this type of problem?
<p>Response ===>
<br> <b>Hmm, usually this means either the kernel's not configured
for SYSV ipc</b>
<br><b> or that you're running in a jail and the sysctl to let the
jail use</b>
<br><b> sysv ipc is not turned on.</b>
<br>
<p>Is this a plausible explanation, & if it is that the kernel's
not configured for SYSV ipc
<br>or that I am running in a jail how can the sysctl be turned on to allow
the jail to use sysv ipc?
<p> Thanks
<p>I've spoken w/ my ISP, Tech. support personnel not quite familiar w/
problem but promised to investigate.
<br>Any other experienced opinions welcomed ...
<p>--- Joe ---
<br>
<br>
<br> </html>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D10B0FD.F0B7F4A5>
