From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Eric Leblond <eric@inl.fr>
Subject: Re: [ANNOUNCE] ulogd 2.0.0beta3
Date: Sun, 08 Mar 2009 13:45:54 +0100 [thread overview]
Message-ID: <49B3BE02.9010203@netfilter.org> (raw)
In-Reply-To: <20090307103406.GB4678@prithivi.gnumonks.org>
Harald Welte wrote:
> Hi guys,
>
> congratulations on the new beta release.
>
> On Fri, Mar 06, 2009 at 07:09:36PM +0100, Pablo Neira Ayuso wrote:
>> Link ulogd2 with libpthread
>
> I was just reading this and all alarm sirens went on. I don't know
> why that is neccessary, and I hope it is just due to some library dependency.
>
> When I created ulogd and ulogd2, I never intended them to become some kind of
> multi-threaded monster with a complex locking and synchronization nightmare.
Please, don't worry, I will not allow such a crappy design change :)
The conntrack-tools follows the sample principle. I don't know if you
had the time to look at the code, but for example, we removed another
tricky issue from the synchronization point of view time ago which was
the use of SIGALARM to implement the timer framework. So this whole
thing now follows an event-driven design with a synchrnous alarm
framework to avoid complexity as expected.
> Sure, I'm no longer maintaining it, and I respect the decision of current
> maintainers, but I just wanted to point that out.
As said, it seems that the patch was applied by Pierre (via Eric) due to
some very kiddish reason, please, set alarms off :).
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2009-03-08 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 18:09 [ANNOUNCE] ulogd 2.0.0beta3 Pablo Neira Ayuso
2009-03-07 10:34 ` Harald Welte
2009-03-07 14:43 ` Jan Engelhardt
2009-03-08 9:53 ` Pierre Chifflier
2009-03-08 12:33 ` Pablo Neira Ayuso
2009-03-08 13:24 ` Harald Welte
2009-03-08 12:45 ` Pablo Neira Ayuso [this message]
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=49B3BE02.9010203@netfilter.org \
--to=pablo@netfilter.org \
--cc=eric@inl.fr \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.