From owner-freebsd-hackers Thu Oct 5 18:47:31 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA02734 for hackers-outgoing; Thu, 5 Oct 1995 18:47:31 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA02729 for ; Thu, 5 Oct 1995 18:47:28 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA00522; Thu, 5 Oct 1995 18:46:01 -0700 From: Terry Lambert Message-Id: <199510060146.SAA00522@phaeton.artisoft.com> Subject: Re: Fiskars UPS support... To: chuckr@eng.umd.edu (Chuck Robey) Date: Thu, 5 Oct 1995 18:46:01 -0700 (MST) Cc: terry@lambert.org, j@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Oct 5, 95 09:35:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1051 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > I wanted to do a program myself like this, but I was hung up on one > question. Many UPSs are going to be used to monitor more than one > machine, so such a program (it seems to me) is going to have to have a > local monitoring part, and a remote 'I take orders' part. This thing is > going to be on the network, then, and have the ability to shut machines > down, directly or indirectly. How then is security controlled? > > It's not too tough a problem on the machine that listens to the UPS port, > but on the other machines, I don't see it clearly. The async port is two > way, so only one machine at a time can talk to it. 1) Assume the host that monitors the thing is up if the thing is up. 2) Make a TCP connection to a priveledged port on that host. Retry at intervals if necessary. 3) It writes you on the connection you made when it wants to notify you of some event. Fairly easy. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.