Date: Mon, 6 Apr 2009 21:08:41 +0000 (UTC) From: Duane Hill <d.hill@yournetplus.com> To: freebsd-questions@freebsd.org Subject: Re: jail stop Message-ID: <alpine.BSF.2.00.0904062107360.46407@duane.dbq.yournetplus.com> In-Reply-To: <6ae50c2d0904061310v14fdb088l8b1c676a2de2f08e@mail.gmail.com> References: <6ae50c2d0904061227t3af4bc8bk648125964cdad5f7@mail.gmail.com> <1239046955.16390.2197.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <49DA5CE1.7060504@gmail.com> <6ae50c2d0904061310v14fdb088l8b1c676a2de2f08e@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Mon, 6 Apr 2009, alexus wrote:
> On Mon, Apr 6, 2009 at 3:49 PM, Adam Vandemore <amvandemore@gmail.com> wrote:
>> Brian A. Seklecki wrote:
>>>
>>> On Mon, 2009-04-06 at 15:27 -0400, alexus wrote:
>>>
>>>>
>>>> cannot stop jail mx. No jail id in /var/run
>>>>
>>>
>>> $ uname -a
>>> There were problems with TTY code in older versions that would cause
>>> processes to get stuck, ghosting jails.
>>>
>> I believe I have seen other causes of this issue since it happens on 7.1.
>> jkill takes care of it. Probably happens due to user error, here at least.
>
> dd# jkill
> jkill: Command not found.
> dd#
>
> i assume jkill isn't part of standard OS, right?
Correct. It can be found here:
/usr/ports/sysutils/jkill
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0904062107360.46407>