From owner-freebsd-hackers Thu May 16 0:40:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 4587937B403 for ; Thu, 16 May 2002 00:40:40 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g4G7aiN78387 for ; Thu, 16 May 2002 00:36:44 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Thu, 16 May 2002 00:36:44 -0700 (PDT) From: Patrick Thomas To: Subject: reboot your own jail ? Message-ID: <20020516003127.I17484-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG currently I reboot jails with this process: 1. someone logs into the jail and runs `kill -KILL -1` 2. someone logs onto the BASE machine and starts it up again. I wish I could do this without involving the admin of the base machine. Has anyone come up with a strategy for allowing the root jail user to successfully reboot their own jail without outside help ? I can think of some horrible hacks involving constantly checking if the jail is running....and if it ever stops (presumably someone rebooted it) then start it again...hopefully there is sonhmething more elegant than that. --pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message