View | Details | Raw Unified | Return to bug 181794
Collapse All | Expand All

(-)jexec.8 (+36 lines)
Lines 84-86 Link Here
84
has a similar race as another process can stop the jail and
84
has a similar race as another process can stop the jail and
85
start another one after the user looked up the
85
start another one after the user looked up the
86
.Ar jid .
86
.Ar jid .
87
.Pp
88
If a forwarding information base (FIB, routing table) has been set 
89
within a jail using the 
90
.Ar exec.fib 
91
parameter, the 
92
.Nm 
93
utility does not honour it, and
94
.Ar command 
95
will be executed using the default fib (usually fib 0).  This can confuse users
96
of jails when trying to troubleshoot jail packet flows.  To properly
97
execute a command in a fib-configured jail using the 
98
.Nm
99
utility, it must be
100
prefixed with the 
101
.Xr setfib 1 
102
utility as follows.
103
.Pp
104
.Dl "setfib -F 1 jexec testjail netstat -rn"
105
or
106
.Dl "setfib 1 jexec testjail netstat -rn"
107
.Pp
108
where testjail has been assigned fib 1 in 
109
.Xr jail.conf 5
110
as follows:
111
.Bd -literal -offset indent
112
testjail {
113
        path = /tmp/jail/testjail;
114
        mount.devfs;
115
        host.hostname = testhostname;
116
        ip4.addr = 192.0.2.100;
117
        exec.fib = 1;
118
        interface = ed0;
119
        exec.start = "/bin/sh /etc/rc";
120
        exec.stop = "/bin/sh /etc/rc.shutdown";
121
}
122
.Ed

Return to bug 181794