Date: Tue, 9 Dec 2008 22:50:52 +0100 From: Henrik Brix Andersen <brix@FreeBSD.org> To: freebsd-embedded@freebsd.org Subject: Re: How to notify for maintenance Message-ID: <20081209215052.GC42936@tirith.brixandersen.dk> In-Reply-To: <734FD4D0-D897-4742-B7A7-E4BA42AB39D7@jump-ing.de> References: <DE033AA5-3C9A-443E-98EB-D313F8BF13EA@jump-ing.de> <20081209200929.GA42936@tirith.brixandersen.dk> <734FD4D0-D897-4742-B7A7-E4BA42AB39D7@jump-ing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--xo44VMWPx7vlQ2+2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 09, 2008 at 10:29:37PM +0100, Markus Hitter wrote: > Am 09.12.2008 um 21:09 schrieb Henrik Brix Andersen: >=20 > > Turn the scenario the other way around and have the trusted 'remote' > > computer initiate the maintenance at given intervals? >=20 > The unfortunate thing I forgot is, the web server is the only one =20 > meant to run around the clock. All others go to sleep, but can be =20 > woken on demand (by a special network ping). How about making them wake-up on a timer event instead? Many BIOS'es support this. If this isn't good for you, you could perform the WoL as described above and still have the trusted, newly awakened host initiate the connection. Brix --=20 Henrik Brix Andersen <brix@FreeBSD.org> --xo44VMWPx7vlQ2+2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) Comment: GnuPG signed iEYEARECAAYFAkk+6DsACgkQv+Q4flTiePgM4ACfUI8vWZUM3FdTro5VXbLhFzMx RDEAn1cfkA/u60+jpVhJhQhwEIMlFlaV =dBEK -----END PGP SIGNATURE----- --xo44VMWPx7vlQ2+2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081209215052.GC42936>