From owner-freebsd-current@FreeBSD.ORG Fri Apr 7 19:53:14 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 DDF8816A400 for ; Fri, 7 Apr 2006 19:53:14 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outbound7.internet-mail-service.net (outbound7.internet-mail-service.net [216.240.47.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8356543D79 for ; Fri, 7 Apr 2006 19:53:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by outbound.internet-mail-service.net (Postfix) with ESMTP id 2DC6F24DCF4; Fri, 7 Apr 2006 12:53:12 -0700 (PDT) Received: from [10.251.19.131] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id k37JrBFd090488; Fri, 7 Apr 2006 12:53:11 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <4436C31A.80006@elischer.org> Date: Fri, 07 Apr 2006 12:52:58 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Guibert de Bruet References: <443310BF.4030600@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:53:14 -0000 Andre Guibert de Bruet wrote: > 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! :) the first part of the patch is not required.... Included by accident. > > 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 */ >