Date: Tue, 12 Jul 2022 17:22:46 +0200 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: Eugene Grosbein <eugen@grosbein.net>, src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 6452fb1e87ed - main - protect.1: Document that protect(1) does not work in jails Message-ID: <e7e882cf-d6df-6239-9345-666facda60e5@FreeBSD.org> In-Reply-To: <f7bf79f5-db75-2b6b-f37c-2bd79c1409cc@grosbein.net> References: <202207112249.26BMn2M4035013@gitrepo.freebsd.org> <f7bf79f5-db75-2b6b-f37c-2bd79c1409cc@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/07/2022 15:51, Eugene Grosbein wrote: > 12.07.2022 5:49, Mateusz Piotrowski wrote: > >> protect.1: Document that protect(1) does not work in jails >> >> The reason is that in order to protect a process procctl(2) needs >> the PRIV_VM_MADV_PROTECT privilege, which is currently denied in jails >> (see kern_jail.c). >> >> > Does it mean that syslogd_oomprotect="YES" in /etc/defaults/rc.conf is inappropriate for full-blown jail > and results in failure of syslogd startup in such jail with defaults? > > *_oomprotect is currently silently ignored inside jails. See rc.subr for the implementation and recent changes to rc.conf(5) for additional details. Best, Mateusz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e7e882cf-d6df-6239-9345-666facda60e5>