ezjail with vimage
Bjoern A. Zeeb
bzeeb-lists at lists.zabbadoz.net
Mon Dec 7 20:45:07 UTC 2009
On Mon, 7 Dec 2009, Miroslav Lachman wrote:
> Bjoern A. Zeeb wrote:
>> On Mon, 7 Dec 2009, Miroslav Lachman wrote:
>>
>> Hi Miroslav,
>>
>>> The last time I wrote with Bjoern A. Zeeb about jailname, cpuset etc.
>>> support in rc.conf (back in March 2009) he stated that "there is no
>>> need to add anything" because it can be done by jail_NAME_flags.
>>> AFAIK current system still doesn't allow me to set cpuset to jail from
>>> rc.conf
>>
>> Check /etc/defaults/rc.conf for jail_example_exec_afterstart.
>
> You already said that in the past and it was the reason why I found bug in
> cpuset.
> http://lists.freebsd.org/pipermail/freebsd-jail/2009-April/000830.html
>
> As I said, exec_afterstart is executed inside the jail and it means that I
> can not use it to bind the jail to specific CPU cores.
> ...but maybe I am blind.
>
> Can you correct me if I am wrong?
*mumble* *tired* *again* ..
Let me cite man rc.conf to not mess it up again:
jail_<jname>_exec_afterstart<N>
(str) Unset by default. This is the command run as Nth com-
mand in a jail after jail startup, where N is 1, 2, and so
on.
jail_<jname>_exec_poststart<N>
(str) Unset by default. This is the command run as Nth com-
mand after jail startup, where N is 0, 1, and so on. It is
run outside the jail.
HTH
/bz
--
Bjoern A. Zeeb It will not break if you know what you are doing.
More information about the freebsd-jail
mailing list