From owner-freebsd-questions Thu Nov 5 04:37:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04404 for freebsd-questions-outgoing; Thu, 5 Nov 1998 04:37:12 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from support.centercomp.com ([206.129.174.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04399 for ; Thu, 5 Nov 1998 04:37:09 -0800 (PST) (envelope-from eric@clean.net) Received: from snmp (midgard-13.PEAK.ORG [198.68.22.77]) by support.centercomp.com (8.8.5/8.8.5) with SMTP id EAA22644 for ; Thu, 5 Nov 1998 04:33:49 -0800 (PST) Message-Id: <4.1.19981105043545.0092d8c0@clean.net> X-Sender: eric@clean.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 (Demo) Date: Thu, 05 Nov 1998 04:36:50 -0800 To: questions@FreeBSD.ORG From: Eric Hake Subject: Best way to monitor a remote unix box? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings! I've got a situation where I am going to be installing headless bsd boxes in a couple of client locations, to act as a simple transaction processing unit. It may get to the point where I will have several hundred of these boxes across the country, and so the thought of logging into each one to see if they're still healthy is less than desirable :) I'm going to be using FreeBSD on the remote end, since that is what I am most familiar with :) My question is this: What is the best way to remote monitor each of these boxes from a central NOC, so I can be alerted of problems as they develop? How do the big guys handle their downstreams? Thanks! Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message