From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Larry Doolittle <ldoolitt@recycle.lbl.gov>
Cc: supervision@list.skarnet.org
Subject: Re: svlogd research
Date: Fri, 16 Nov 2007 15:10:44 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711161505260.9811@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20071116195717.GA10933@recycle.lbl.gov>
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. The mirror algorithm could use the fact that
'current' can only grow or be renamed. IIUC, all you need to do is send
any log file not already on the remote server and then send either all of
current, or the balance of current, depending on whether rotation has
occurred since the last mirror cycle.
Or you could just rsync, which will be a little more wasteful.
next prev parent reply other threads:[~2007-11-16 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 19:57 Larry Doolittle
2007-11-16 20:10 ` Charlie Brady [this message]
2007-11-16 20:23 ` Larry Doolittle
2007-11-16 22:08 ` George Georgalis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0711161505260.9811@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=ldoolitt@recycle.lbl.gov \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).