Date: Sat, 16 Jul 2011 21:26:53 -0700 From: Gary Kline <kline@thought.org> To: Ryan Coleman <editor@d3photography.com> Cc: Bill Tillman <btillman99@yahoo.com>, freebsd-questions@freebsd.org Subject: Re: how to force a hard reboot remotely Message-ID: <20110717042653.GA28019@thought.org> In-Reply-To: <CAC724AA-7EDB-427E-9EE7-CE2969775026@d3photography.com> References: <CAGBxaXnz3cD6ZKaDiDW_YEWpdhwjkAUBLM07T0_2NkpGc5QfmA@mail.gmail.com> <1310873512.63641.YahooMailRC@web36508.mail.mud.yahoo.com> <CAC724AA-7EDB-427E-9EE7-CE2969775026@d3photography.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 16, 2011 at 10:39:06PM -0500, Ryan Coleman wrote: > Date: Sat, 16 Jul 2011 22:39:06 -0500 > From: Ryan Coleman <editor@d3photography.com> > Subject: Re: how to force a hard reboot remotely > To: Bill Tillman <btillman99@yahoo.com> > Cc: freebsd-questions@freebsd.org > X-Mailer: Apple Mail (2.1084) > > When bottom replying, please clear the header and signature - thanks. > > You can set up a BIOS boot time, if you can get onsite... that would allow you to power it down at, say, 11:59PM and have it power back on at Midnight. > > Or a UPS that's controlled by another machine. Or the magic packet WOL option... but those require another machine. Maybe a switch or router than can send WOL packets would be a possibility? > > -- > Ryan I had something like this in late 1995. Remotely "shutdown -h [time]" got my box powered down, then a remote timer cycled the power. Problems were: that the timer was hard to set exacrly. [There may have ben two timers; it was a bear of a problem. ] gary > > On Jul 16, 2011, at 10:31 PM, Bill Tillman wrote: > > > > > WOW! That's a tall order. A reboot from remote is simple, but a cold boot....I > > don't think that's possible unless you have some kind of Wake-On-Lan capable NIC > > which could detect a connection attempt while the machine is off. I can't say > > that for sure because what you've got to remember is that with a cold boot, the > > machine will no longer remember what OS it was running until it reboots. My > > advice would be to get to the console if you absolutely have to cold boot it. Or > > call someone nearby the console and have the actually turn the machine off, wait > > the obligatory 30 seconds and then restart it. Someone else may have a better > > idea. > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- Gary Kline kline@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110717042653.GA28019>