New jail(8) with configuration files, not yet in head

[Brandon Gooch]

On Mon, Jul 4, 2011 at 4:50 PM, Jamie Gritton <jamie at freebsd.org> wrote:
> Oh, never good when "(null)" shows up. I'll see what I'm trying to run
> that isn't there.
>
> - Jamie
>
>
> On 07/04/11 15:36, Brandon Gooch wrote:
>>
>> I did however notice a minor nit in the output when removing a jail.
>> Here's the scenario:
>
> ...
>>
>> Now, when I go to remove the jail:
>>
>> # jail -r ports
>> Stopping cron.
>> Waiting for PIDS: 29824.
>> Terminated
>> .
>> jail: ports: (null): failed
>>
>> I don't think it's anything to worry about, as the jail does indeed
>> get removed. I wonder though if this might be a indicator of some
>> underlying problem I haven't ran into yet with my simplistic testing.
>

Thanks for checking it out. Here's another take on perhaps the same
underlying issue.

If I've jexec'd into the jail, say something like this:

# jexec testjail /bin/tcsh

and then I try removing the jail from another terminal (jail -r
testjail), the jail -r command hangs for about 15-20 seconds, I
suppose waiting for the jexec'd shell to exit, before finally killing
the jail off outright. I don't see the aforementioned behavior (jail:
testjail: (null): failed).

Here's what it looks like:

# jail -r ports
Stopping ftpd.
Waiting for PIDS: 32845.
Stopping cron.
.
Terminated
^T
load: 0.19  cmd: jail 32860 [kqread] 1.05r 0.00u 0.00s 0% 1696k
^T
load: 0.09  cmd: jail 32475 [kqread] 10.09r 0.00u 0.00s 0% 1692k

...then testjail is finally "Killed". Some sort of race condition maybe?

-Brandon