public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: dev-db/libdbi-0.8.3 failed
Date: Tue, 8 Sep 2009 15:30:11 +0000 (UTC)	[thread overview]
Message-ID: <pan.2009.09.08.15.30.11@cox.net> (raw)
In-Reply-To: 200909071534.02473.gentoo@appjaws.plus.com

Paul Stear posted on Mon, 07 Sep 2009 15:34:02 +0100 as excerpted:

> Thanks Duncan, that was the problem.  I put an entry in package.use and
> all is well libdbi is not now required.  As far as I know I do not need
> sql for syslog-ng which I have been using for years without any problem.
>  I wonder if this is a new flag for that program.

It seems to be, yes.  A quick epkginfo to see what versions are available 
says there's a 2.0 and a 2.1 version in-tree, in addition to the 3.x 
version that's new.  A quick emerge -pv =<version> on the 2.x versions 
did indeed show the flag as disappearing, so it must be new, or at least 
newly unmasked.

But there's a few other changes with the 3.x version as well.  I have a 
bit of a customized syslog config, spitting out various messages to 
specific files and filtering a few of them, and I had to google for a 
couple of the new features as it was protesting that the ones I was using 
were deprecated and not particularly well performing.

But the sql thing is either for hyper-control people (and I thought /I/ 
was bad!) or more practically, for those using a syslog server to manage 
a few hundred or thousand machines.  In that case, yes, I could see how a 
database backend could be /quite/ helpful indeed!  But I don't see any 
reason for someone running it for just their own machine, or even for 2-3 
machines on a home network, to need the extra complexity of the database 
setup.  Maybe at a half-dozen or so machines, if they're all logging to a 
central server...

Anyway, to maybe save you some trouble if you have multiple filters 
configured, the former match filter is now much broader.  To get similar 
functionality to the previous, simply s/match/message/.  Other than that, 
and the SQL building problems you experienced, it seems to be pretty much 
the same, tho somewhat more powerful than it was if you need it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2009-09-08 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07  8:06 [gentoo-amd64] dev-db/libdbi-0.8.3 failed Paul Stear
2009-09-07 13:22 ` [gentoo-amd64] " Duncan
2009-09-07 14:34   ` Paul Stear
2009-09-08 15:30     ` Duncan [this message]
2009-09-08 16:55       ` Frank Peters
2009-09-07 14:39 ` [gentoo-amd64] " Frank Peters

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=pan.2009.09.08.15.30.11@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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