On Sun, Nov 28, 2004 at 12:00:58PM +, [EMAIL PROTECTED] wrote:
> From: Justin Hopper <[EMAIL PROTECTED]>
>
> I know that Pawel @ http://garage.freebsd.pl has a patch for making
> private SysV IPC memory spaces for the host system and each jail:
>
> http://garage.freebsd.pl/privipc.README
>
>
On Sat, 2004-Nov-27 21:43:09 +0100, Koen Martens wrote:
>Why would one want access from the outside system to the jailed system?
>Is this something that is used frequently?
The sysadmin is likely to need access to:
1) look at SysV IPC usage across the entire system
2) clean up after a process has
On Fri, 2004-11-26 at 11:38, Koen Martens wrote:
> Hello Hackers,
>
> For a while i've been wanting shared memory to be usable withing jails,
> but with cross-jail protection. Ie. shared memory is restricted to a
> jail.
>
> Recently I've been digging a bit in the freebsd kernel source code
> (w
On Fri, Nov 26, 2004 at 10:58:43PM +0100, Jilles Tjoelker wrote:
> You will have trouble if two jails want to use the same IPC key (key_t,
> usually a long). This can also happen in rare cases when running
> multiple programs (unjailed) that all try to use separate SysV IPC.
Hmm.. Yes..
> In the
On Fri, Nov 26, 2004 at 08:38:00PM +0100, Koen Martens wrote:
> For a while i've been wanting shared memory to be usable withing jails,
> but with cross-jail protection. Ie. shared memory is restricted to a
> jail.
> Recently I've been digging a bit in the freebsd kernel source code
> (which is n
Hello Hackers,
For a while i've been wanting shared memory to be usable withing jails,
but with cross-jail protection. Ie. shared memory is restricted to a
jail.
Recently I've been digging a bit in the freebsd kernel source code
(which is new to me, been doing quite some linux kernel hacking tho
6 matches
Mail list logo
