From owner-freebsd-embedded@FreeBSD.ORG Tue Dec 9 21:50:55 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A7CD1065670 for ; Tue, 9 Dec 2008 21:50:55 +0000 (UTC) (envelope-from brix@FreeBSD.org) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 572AD8FC13 for ; Tue, 9 Dec 2008 21:50:55 +0000 (UTC) (envelope-from brix@FreeBSD.org) Received: from tirith.brixandersen.dk (0x55534f5f.adsl.cybercity.dk [85.83.79.95]) by solow.pil.dk (Postfix) with ESMTPA id 356831CC1B0 for ; Tue, 9 Dec 2008 22:50:54 +0100 (CET) Received: by tirith.brixandersen.dk (Postfix, from userid 1001) id C4EFB1141D; Tue, 9 Dec 2008 22:50:52 +0100 (CET) Date: Tue, 9 Dec 2008 22:50:52 +0100 From: Henrik Brix Andersen To: freebsd-embedded@freebsd.org Message-ID: <20081209215052.GC42936@tirith.brixandersen.dk> References: <20081209200929.GA42936@tirith.brixandersen.dk> <734FD4D0-D897-4742-B7A7-E4BA42AB39D7@jump-ing.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xo44VMWPx7vlQ2+2" Content-Disposition: inline In-Reply-To: <734FD4D0-D897-4742-B7A7-E4BA42AB39D7@jump-ing.de> X-PGP-Key: http://www.brixandersen.dk/files/HenrikBrixAndersen.asc User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: How to notify for maintenance X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 21:50:55 -0000 --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 --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--