From owner-freebsd-current@FreeBSD.ORG Fri Apr 7 19:44:31 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B332916A400 for ; Fri, 7 Apr 2006 19:44:31 +0000 (UTC) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EFB943D48 for ; Fri, 7 Apr 2006 19:44:31 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from [10.7.6.254] ([63.76.235.163]) by lexi.siliconlandmark.com (8.13.3/8.13.3) with ESMTP id k37JiEBC067838; Fri, 7 Apr 2006 15:44:14 -0400 (EDT) (envelope-from andy@siliconlandmark.com) In-Reply-To: <443310BF.4030600@elischer.org> References: <443310BF.4030600@elischer.org> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andre Guibert de Bruet Date: Fri, 7 Apr 2006 15:43:03 -0400 To: Julian Elischer X-Mailer: Apple Mail (2.749.3) X-Information: Please contact the ISP for more information X-SL-MailScanner: Found to be clean X-SL-SpamCheck: not spam, SpamAssassin (score=-1.457, required 6, BAYES_00 -2.60, SPF_FAIL 1.14) X-MailScanner-From: andy@siliconlandmark.com Cc: current@freebsd.org Subject: Re: change to syslog to allow specifying prot to send to.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 19:44:31 -0000 On Apr 4, 2006, at 8:35 PM, Julian Elischer wrote: > Does anyone think that this would be useful? > > the syslog.conf line would look like: > > > *.* @logger.mynet.com:823 Off the top of my head, there are two scenarios that I see this useful in: - Forwarding log messages to a secure syslog server, on a non- privileged port (I think everyone agrees that reducing the number of root-run services is a good thing). - Logging to a remote syslog over a local port, forwarded over an ssh tunnel (To an off-site centralized logging server, for example), while still having local logging enabled. I have been looking for this type of functionality for a little while now. I was about to look into coding it. Thanks! :) Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */