Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Apr 2006 12:40:53 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        "Marc G. Fournier" <scrappy@hub.org>, freebsd-stable@freebsd.org, freebsd-current@freebsd.org, pjd@freebsd.org
Subject:   Re: new feature: private IPC for every jail
Message-ID:  <44317A45.9000504@elischer.org>
In-Reply-To: <20060403163220.F36756@fledge.watson.org>
References:  <20060403003318.K947@ganymede.hub.org> <20060403163220.F36756@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote:

>
> On Mon, 3 Apr 2006, Marc G. Fournier wrote:
>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/48471
>>
>> [kernel] [patch] new feature: private IPC for every jail
>>
>> Its an ancient, 4.x patch for having private IPC in a jail ... not 
>> sure how hard it would be to bring it up to 6.x / -current standards 
>> though ... but it seems like something 'good' that is needed ...
>
>
> In the past I've looked at doing things along these lines, but usually 
> stall after a first hack when trying to decide how to deal with two 
> critical issues:
>
> (1) The fact that system v ipc primitives are loadable, and 
> unloadable, which
>     requires some careful handling relating to registration order, etc.


this is related to the problem that needs to be solved for getting 
vimage into -current.

>
> (2) The name space model for system v ipc is flat, so while it's 
> desirable to
>     allow the administrator in the host environment to monitor and 
> control
>     resource use in the jail (for example, delete allocated but unused
>     segments), doing that requires developing an administrative model 
> for it.


it is possible the admin environment can't see it.
unless you prefix it with something..

>
> These challenges can be surmounted, but the doing them in a nice way 
> requires some thought.
>
> Robert N M Watson
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44317A45.9000504>