From owner-freebsd-hackers Fri Apr 21 1:19:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tofu.alt.net (tofu.alt.net [207.14.113.2]) by hub.freebsd.org (Postfix) with ESMTP id E325D37B8DD for ; Fri, 21 Apr 2000 01:19:28 -0700 (PDT) (envelope-from abourov@alt.net) Received: from comp3 ([209.152.191.211]) by tofu.alt.net (8.9.3/8.8.5) with ESMTP id BAA15063 for ; Fri, 21 Apr 2000 01:17:34 -0700 (PDT) Message-Id: <4.2.0.58.20000421010847.01c3ae50@mail3.addr.com> X-Sender: abourov@mail.alt.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 21 Apr 2000 01:16:56 -0700 To: freebsd-hackers@FreeBSD.ORG From: Anthony Bourov Subject: Intel's GX managment port client, or any hints on the specs? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We host a whole bunch of servers, all FreeBSD, and many of them run on intel GX motherboards, which have a feature called EMP. Basically, I didn't go to much detail into this, I got that it is a way to monitor/control the server through modem/null-modem client. But they provide their own client-NT/95 only of course, and it didn't look like the communication is clear text. Does anyone know if anyone was planning to write something for this, or if there are specs available. I probably don't need the know monitoring thing, just a way to do a remote reset. In general, are there any good remote reset solutions, one that would invoke a hard reset, but not one of those that will completely cut the power to the server, and then turn it back on, I found that it's pretty likely to get problems if you use that enough. Thanks, Anthony Ps. if you respond to the mailing list, could you also CC the responses to my email address as I barely have time to catch up with all my email, and probably not the mailing list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message