postgreSQL on freeNAS jail - sysctl security.jail.sysvipc_allowed not working

[Carmageddon]

Hi guys,

I am trying to run postgres on freenas 9.3 stable, using the following cmd:

root@Dev:/ # /usr/local/etc/rc.d/postgresql initdb
The files belonging to this database system will be owned by user "pgsql".
This user must also own the server process.

The database cluster will be initialized with locale "C".
The default text search configuration will be set to "english".

Data page checksums are disabled.

creating directory /usr/local/pgsql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 400kB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
creating template1 database in /usr/local/pgsql/data/base/1 ... FATAL: could not create shared memory segment: Function not implemented
DETAIL: Failed system call was shmget(key=1, size=48, 03600).
child process exited with exit code 1
initdb: removing data directory "/usr/local/pgsql/data"

I have been reading here:
http://www.freebsddiary.org/jail-multiple.php
Here: https://forums.freenas.org/index.php?threads/postgresql-in-plugin-jail.9058/
And here: https://jasonk2600.wordpress.com/2010/01/11/installing-postgresql-on-freebsd/

but all my attempts failed, after reboot the value on host freenas is lost.
I can set it manually as sysctl security.jail.sysvipc_allowed=1 and restarting the jail above, but error stays the same.

I have now added that value via freeNAS gui into system>turnable, but it doesn't help as it has only solve the persistence problem after a reboot.

 

[Carmageddon]

Ok I think I resolved this, had to edit jail settings in freeNAS GUI, and add allow.sysvipc=1 to proper place, restarted jail, and setting works!
Now jsut to figure out how to start the DB at boot, and configure it...