https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209112
d...@araxis.com changed:
What|Removed |Added
CC||d...@araxis.com
--- Comment #4 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209112
--- Comment #5 from d...@araxis.com ---
I should also like to add my voice to those requesting logging of boot-time
jail startup problems. The lack of any diagnostics cost me several hours of
time in tracking down this problem.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209112
--- Comment #6 from d...@araxis.com ---
I have what seems (on first try, at least) to be a viable alternative
workaround that is (somewhat) less icky than adding artificial dependencies
between jails. Simply add the following two lines to /e
I have the following in my jail.conf:
devfs_ruleset = 4;
vpn1 {
ip4.addr = 10.70.5.254;
ip4.addr += "tun0|10.70.5.1 10.70.5.254 mtu 1500 netmask
255.255.255.255";
interface = lagg0;
devfs_ruleset = 5;
}
I expect that in the jail both rules 4 and 5 are active. How can I check
that?
Not so. The top variable, devfs_ruleset = 4 is being set as the default for
all jails. The devfs_ruleset = 5 inside the brackets is changing the
default value.
How to check what ruleset is mounted? That is a great question. I'm not
sure of an easy way to check other than verifying the /dev directo
