From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1573 Path: news.gmane.org!not-for-mail From: George Georgalis Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: svlogd research Date: Fri, 16 Nov 2007 17:08:24 -0500 Message-ID: <20071116220824.GM22612@run.duo> References: <20071116195717.GA10933@recycle.lbl.gov> <20071116202313.GA11216@recycle.lbl.gov> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1195250920 17713 80.91.229.12 (16 Nov 2007 22:08:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 Nov 2007 22:08:40 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-1808-gcsg-supervision=m.gmane.org@list.skarnet.org Fri Nov 16 23:08:44 2007 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.50) id 1It9Me-0008RA-2e for gcsg-supervision@gmane.org; Fri, 16 Nov 2007 23:08:40 +0100 Original-Received: (qmail 17695 invoked by uid 76); 16 Nov 2007 22:08:43 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 17690 invoked from network); 16 Nov 2007 22:08:43 -0000 Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20071116202313.GA11216@recycle.lbl.gov> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1573 Archived-At: On Fri, Nov 16, 2007 at 12:23:13PM -0800, Larry Doolittle wrote: >Friends - > >On Fri, Nov 16, 2007 at 03:10:44PM -0500, Charlie Brady wrote: >> On Fri, 16 Nov 2007, Larry Doolittle wrote: >> >>> I want both a reliable local log, and an encrypted (via stunnel) remote >>> log, where I can't control the reliability of the remote logging machine >>> (or the network path to it). >> >> My recommendation is that you log locally and periodically (often) mirror >> the log directory remotely. > >Interesting suggestion. I can't easily use it, because I also don't >control the software running on the remote logging machine -- it is >syslogd wrapped in SSL, non-negotiable. in addition to your local log dir, you could also write to a fifo where another program reads and writes to your remote syslogd. Of course if you loose the remote connection there could be a blocking issue. another way is to use a processor to send log entries at rotation time, and sent the alarm signal to the log daemon at what ever interval you need to keep the remote updated. again, if you cannot connect there will be a block, when you try to alarm the next time. yet another way is to use a processor to signal another program to start the remote connection and dump the new logfile (by alarm if necessary). that could be done any number of ways and wouldn't block if it failed, but watch out that svlogd doesn't rotate away log files that haven't been transferred yet. // George -- George Georgalis, information system scientist <