Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Jan 2009 10:15:36 -0800
From:      "Garrett Cooper" <yanefbsd@gmail.com>
To:        "Shane Ambler" <FreeBSD@shaneware.biz>
Cc:        "Niels S. Eliasen" <nse@delfi-konsult.com>, freebsd-ppc@freebsd.org
Subject:   Re: How to make a remote reboot when system has panic'ed ?
Message-ID:  <7d6fde3d0901121015q75b2d85fw4b9b58a4edca09b7@mail.gmail.com>
In-Reply-To: <496B6DD6.3000501@ShaneWare.Biz>
References:  <5C255016-E6FF-4350-82E5-4833C3CD05F5@delfi-konsult.com> <496B53B2.3090604@freebsd.org> <496B6DD6.3000501@ShaneWare.Biz>

index | next in thread | previous in thread | raw e-mail

On Mon, Jan 12, 2009 at 8:20 AM, Shane Ambler <FreeBSD@shaneware.biz> wrote:
> Nathan Whitehorn wrote:
>>
>> Niels S. Eliasen wrote:
>>>
>>> hi guys
>>> Having some issues with the current kernel getting sound and keyboard
>>> working (thanks sofar Nathan! ) made me think about how to reboot when the
>>> system has panic'ed...  remotely ??
>>> ie. a virtual CTRL-OPTION-POWER ?
>>> is that possible at all?
>>
>> How remotely? During a panic, there is necessarily no network access.
>> Typing reset at the debugger prompt, though, via a serial console or
>> firewire (dcons) will cause a reboot, and the machine with the other end of
>> the console can be connected to the network.
>>
>>> and at the same time.... How about a automatic reboot after a
>>> power-outage ? (the option is available within MacOSX/YDL Linux as well) ??
>>> just rambling ....
>>
>> See the sysctl dev.pmu.0.server_mode.
>> -Nathan
>
> May not help - but then it may point your thoughts the right way -
>
> Dedicated Hosting services have been known to provide remote access (either
> web or telnet access) to the UPS powering your server allowing a power cycle
> as needed. Combined with a remote console access (think second pc with
> serial port connection to the server in question) allowing single user
> booting to swap kernels from across the globe.
>
> X10 home automation anyone??

>From my kernel config file:

# Debugging for use in -current
options         KDB                     # Enable kernel debugger support.
options         KDB_UNATTENDED          # I don't want to be here when
stuff crashes..

>From /etc/sysctl.conf:
debug.debugger_on_panic=0

Cheers,
-Garrett


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0901121015q75b2d85fw4b9b58a4edca09b7>