Date: Sun, 31 Mar 2013 13:04:26 -0600 From: Jamie Gritton <jamie@FreeBSD.org> To: Dirk Engling <erdgeist@erdgeist.org> Cc: freebsd-jail@FreeBSD.org Subject: Re: rc.d/jail and jail.conf Message-ID: <515888BA.8060804@FreeBSD.org> In-Reply-To: <5158874C.2060701@erdgeist.org> References: <515721F8.9090202@erdgeist.org> <AA7CA531-5197-4BBC-B260-A3EC8B7A1024@inbox.im> <alpine.BSF.2.00.1303302157010.85469@erdgeist.org> <515847AF.8070808@FreeBSD.org> <5158526A.4020400@quip.cz> <51586419.5090207@FreeBSD.org> <51586DC8.7030500@quip.cz> <515880F3.1050300@FreeBSD.org> <5158874C.2060701@erdgeist.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/31/13 12:58, Dirk Engling wrote: > On 31.03.13 20:31, Jamie Gritton wrote: > >> That seems reasonable, but using a jail list in rc.conf may suffice. > > It is less error prone to just use 'jail_list=*' in rc.conf and disable > jails per config block, and then issue a warning like 'Skipping disabled > jail(s) foo, bar, baz'. > > (Although I see this from a perspective of jails being virtual hosts > that should be configurable by automated tools, too.) If you don't mind some slightly difficult error messages, you can always "disable" a jail with exec.prestart="false". jail(8) requires all commands to succeed, and in particular won't even create a jail when one of the prestart commands fails. - Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515888BA.8060804>