Date: Sun, 20 Feb 2022 10:46:56 +0100 From: Jon Clausen <freebsd-questions@ymmv.dk> To: doug <doug@safeport.com> Cc: freebsd-questions@freebsd.org Subject: Re: jail.$jailname.conf not directly in /etc/ ? Message-ID: <20220220094656.3legbf6vs7wfm5vx@c02qx0.local> In-Reply-To: <f9882bc-3ae-b91f-5bbc-22b6a6485c19@safeport.com> References: <20220219092824.6qmzo33es3w73nj5@c02qx0.local> <f9882bc-3ae-b91f-5bbc-22b6a6485c19@safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-02-19 18:46:24 (+0000), doug wrote: > > Any ideas? > > Ezjail and iocage put the jail configuration in different places. Perhaps > man jail is the answer: > > -f conf_file > Use configuration file conf_file instead of the default > /etc/jail.conf. Ah yes, that works when you (or some script) issue the jail command directly. But since I would like to create/setup/destroy/tear down the jails using my own scripts, but leave the start/stop operations to the system rc/service framwork, then using the -f flag is not an option, without modifying various bits of the system, as you point out below > I've never done this. I've used the jail command, ezjail, and iocage I've > always let the tool choose the location of the jail configuration. Moving it > will mean, at a minimum you will have to rewrite the scripts for: starting, > stoping, and console. You will also have to do something with /etc/rc.conf. yeah, nah... this is not how I'd like to proceed. This is much like building a bridge to cross the stream, to get the water. > If it were me, I'd let sleeping jail configs lie :) That's probably good advice, but I'm not quite done prodding the stuff just yet. I see one possible "half way", as I hinted at a minute ago in another reply... br /jon -- YMMV
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220220094656.3legbf6vs7wfm5vx>