On 2021-06-25 09:58, Michael Gmelin wrote:
Another problem caused by the lack of jail ownership is that access
semantics are a bit strange. E.g., a jail based on / can easily list
(and remove) all memory allocations in the system, while for other
jails
it depends. They can stat their own alloca
On 2021-06-25 09:58, Michael Gmelin wrote:
On Fri, 25 Jun 2021 09:19:05 -0700
James Gritton wrote:
On 2021-06-25 07:41, Michael Gmelin wrote:
> It seems like non-anonymous POSIX shared memory is not freed
> automatically when a jail is removed and keeps it in a dying state,
> until the shared
On Fri, 25 Jun 2021 09:19:05 -0700
James Gritton wrote:
> On 2021-06-25 07:41, Michael Gmelin wrote:
> > It seems like non-anonymous POSIX shared memory is not freed
> > automatically when a jail is removed and keeps it in a dying state,
> > until the shared memory segment is deleted manually.
On 2021-06-25 07:41, Michael Gmelin wrote:
It seems like non-anonymous POSIX shared memory is not freed
automatically when a jail is removed and keeps it in a dying state,
until the shared memory segment is deleted manually.
See below for the most basic example:
[root@jailhost ~]# jail -c p
Hi,
It seems like non-anonymous POSIX shared memory is not freed
automatically when a jail is removed and keeps it in a dying state,
until the shared memory segment is deleted manually.
See below for the most basic example:
[root@jailhost ~]# jail -c path=/ command=/bin/sh
# posixshmcont
