Summary: | rc.conf(5): Empty "jail_list" does not start jails defined in "/etc/jail.conf.d" | ||
---|---|---|---|
Product: | Base System | Reporter: | Stephen Fox <stephen.j.fox.jr> |
Component: | conf | Assignee: | freebsd-jail (Nobody) <jail> |
Status: | New --- | ||
Severity: | Affects Some People | CC: | antranigv, crest, jamie, markj, pat |
Priority: | --- | ||
Version: | 13.2-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Stephen Fox
2023-10-18 17:14:27 UTC
It would be nice if it did, but an empty $jail_list just starts the jails in the global /etc/jail.conf. To have per jail jail.conf files in FreeBSD < 14 you need to list them in $jail_list. The least painful way to do this is through `sysrc jail_list+=$name`. Is this just a documentation bug in 13.2? What changed between 13.2 and 14.0 such that this stopped being a problem? Greetings, In FreeBSD 13.2-RELEASE, jail_list="" will start the jails that are defined in jail.conf. If you want to start the jails in jails.conf.d, you have to use jail_list. In FreeBSD 14, the behavior seems to be the same (at least according to the code). However, you can do the following in jail.conf .include("/etc/jail.conf.d/foo.conf") which is better than using jail_list, as it will give you the ability to use features such as depends, multi-layer includes, etc. This, indeed, seems like a bug in documentation. I will fix it. |