| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | debdrup(at)gmail(dot)com |
| Subject: | BUG #15268: Documentation surrounding sysvipc configuration and isolation is out-of-date as of FreeBSD 11 |
| Date: | 2018-07-08 09:50:11 |
| Message-ID: | 153104341110.1408.11582740185774115453@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15268
Logged by: D. Ebdrup
Email address: debdrup(at)gmail(dot)com
PostgreSQL version: 10.0
Operating system: FreeBSD
Description:
Owing to some rather big changes in FreeBSD, the steps recommended in the
documentation for all supported (and unsupported) versions of pgsql on
FreeBSD 11 and future versions regarding sysvipc are no longer accurate.
Notably, the security.jail.sysvipc_allowed sysctl has been marked deprecated
(ie. to be removed in a future version) and the sysvmsg, sysvsem, and
sysvshm properties for jails have been added which can function like
security.jail.sysvipc_allowed/allow.sysvipc used to work, in addition to
which a value named "new" has been added which offers proper per-jail
isolation of SysV messages, semaphores and shadow memory.
This can be confirmed by going to https://man.freebsd.org/jail(8) and
searching for the second result of sysvmsg as a text-search.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-07-08 22:01:58 | Re: BUG #15268: Documentation surrounding sysvipc configuration and isolation is out-of-date as of FreeBSD 11 |
| Previous Message | PG Bug reporting form | 2018-07-08 01:15:25 | BUG #15267: just for test |