From owner-freebsd-stable Sun Jan 6 16:54:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mighty.grot.org (mighty.grot.org [216.15.97.5]) by hub.freebsd.org (Postfix) with ESMTP id DB85037B417 for ; Sun, 6 Jan 2002 16:54:22 -0800 (PST) Received: by mighty.grot.org (Postfix, from userid 515) id 7D27B5E69; Sun, 6 Jan 2002 16:54:17 -0800 (PST) Date: Sun, 6 Jan 2002 16:54:17 -0800 From: "R.P. Aditya" To: "Arthur W. Neilson III" Cc: freebsd-stable@freebsd.org Subject: Re: Could someone commit the change suggested in PR bin/32420? Message-ID: <20020107005417.GA19294@mighty.grot.org> Reply-To: "R.P. Aditya" References: <4.3.2.7.2.20020105145152.01cbc100@localhost> <4.3.2.7.2.20020105005950.00db4f00@localhost> <4.3.2.7.2.20020105145152.01cbc100@localhost> <4.3.2.7.2.20020106163320.00dc1960@localhost> <200201061410150780.48050584@smtp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201061410150780.48050584@smtp> X-PGP-Key: http://www.grot.org/pubkey.asc X-PGP-Key-ID: 0x6405D8D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jan 06, 2002 at 02:10:15PM -1000, Arthur W. Neilson III wrote: > msyslog is pretty cool, it's modular and has a bunch of different input > modules for tcp, udp, streams and unix domain sockets also output > modules for mysql, postgres, peo (hash protection) and regex. it is worth exploring > and actually is BSD licensed, as shown on the freshmeat homepage msyslog does sound very cool, however the following note in the README worries me: Known Bugs ---------- - If a module blocks on I/O the hole daemon blocks, and messages can get lost on extremely busy hosts. so even if a small percentage of syslog messages go to, say mysql or postgres, and the database "goes away" for some reason, then nothing else can syslog -- I use swatch to monitor system status, and wouldn't even receive the warning from my "watcher" script via syslog that the database was unreachable... An alternative would be to run it on a central loghost and have some other alert mechanism for the database on the loghost. Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message