From owner-freebsd-hardware Fri Jun 28 15:54:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05749 for hardware-outgoing; Fri, 28 Jun 1996 15:54:48 -0700 (PDT) Received: from charlotte.spiders.com (charlotte.spiders.com [199.224.7.188]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA05744 for ; Fri, 28 Jun 1996 15:54:45 -0700 (PDT) Received: (from gwh@localhost) by charlotte.spiders.com (8.6.12/8.6.12) id SAA05541; Fri, 28 Jun 1996 18:57:25 -0400 Message-Id: <199606282257.SAA05541@charlotte.spiders.com> From: gwh@spiders.com (Gene W Homicki) Date: Fri, 28 Jun 1996 18:57:25 -0400 In-Reply-To: Sean Kelly's message as of Jun 28, 15:37 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Sean Kelly , brantk@gatekeeper.atlas.com Subject: Re: Devices compatible with tw(4) (X-10) Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk +--- | Brant> I'm interested in doing some experimentation with X-10 | | That's just one way to go. +--- I was just looking for remote power cycling devices (via phone, or whatever else) to manage a machine room while there are no staff around....and this message popped up. Has anyone used the X-10 stuff for this type of application? Is there a better way to go? My idea is to have one phone based power cycle device on the machine that has a dialin and the X-10 based controller. If that machine goes down, you can remotely reboot it. Onc its back up, you can power cycle any other locked up machines... just a thought. If someone has recommendations on a better way to do this, that is cost effective, I'd love to hear about it. --Gene -- Gene W. Homicki gwh@spiders.com Objective Consulting, Inc. http://www.spiders.com/ Internet Presence Design voice: +1 914.353.3511