[Bug 245627] jail rc script stops jails not defined in jail.conf

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627

joeb1 at a1poweruser.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joeb1 at a1poweruser.com

--- Comment #1 from joeb1 at a1poweruser.com ---
Jail definition statements can still be placed in rc.conf which is the pre
release 6.0 method or in the jail.conf file which is the new way since release
6.0. The code in rcd/jail needs to be cleaned up removing the processing of the
old rc.conf jail definition method. ezjail uses the rc.conf method and gets a
warning message telling the user to change his jail definition method to use
jail.conf. The ezjail maintainer has been told to update ezjail many times over
the past 6 releases of FreeBSD but has not done so. qjail is an updated version
of ezjail that uses jail.conf and only starts/stops/restarts jails under it
control. It does not use the default jail.conf file so native jails and other
jail tools do not step on qjail jails.

When it comes to jails with manual defined definitions in the default jail.conf
file with other jail tools also putting their jail definitions in the default
jail.conf file the rc.conf jail start statement will start all of them at boot
time by default as designed. Adding the rc.conf jail names statement containing
the jail names to use is only way to control which jails are started at boot
time by default. 

It is the users responsibility that native jail and jail tools that use the
default jail.conf file DO NOT exist on the same host at the same time because
of the possibility of them stepping on each other during host boot or
stop/restart time. 

To summarize: This is not a bug or short coming in rcd/jail. But a design flaw
in some jail tools making them incapable of playing nice with native jails
defined in the default jail.conf file. This bug report should be closed because
it's not a bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.