From owner-freebsd-questions Fri Nov 6 05:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29668 for freebsd-questions-outgoing; Fri, 6 Nov 1998 05:27:32 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29625 for ; Fri, 6 Nov 1998 05:27:26 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.59.138]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA508; Fri, 6 Nov 1998 14:27:14 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4.1.19981105043545.0092d8c0@clean.net> Date: Fri, 06 Nov 1998 14:31:14 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Eric Hake Subject: RE: Best way to monitor a remote unix box? Cc: questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Nov-98 Eric Hake wrote: > 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? We at my work do compile daily mails of security checkings (UIDs of 0) and df, firewalls logs etc... That might help too... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message