Now libev will be default event handler instead of libevent?

5 January 2009: Wouter
- fixup getaddrinfo failure handling for remote control port.
- added L.ROOT-SERVERS.NET. AAAA 2001:500:3::42 to builtin root hints.
- fixup so it works with libev-3.51 from http://dist.schmorp.de/libev/
- comm_timer_set performs base_set operation after event_add.

Hi Wouter.

I can see from the change log that now Unbound officialy supports also
libev? Do you plan to entirely replace libevent with libev, or libev
will be as an alternative recommended variant for people who got
troubles with libevent?

Hi Beastie,

While working on libev support I found the problem we were seeing with
libevent. It is fixed in current svn trunk, which should make unbound
work fine with many libevent versions.

The problem caused threaded race condition problems. Most of the time
this race condition did not cause a problem. It only happened with
libevent (and also libev, which is specifically supports the nonfeature
involved, and crashed for me so I could debug it).

Haw Loeung graciously tested the fix for me, and reports that his
libevent problems seem to be over.

The fix is scheduled for the upcoming 1.1.2 release.

And yes the idea was to support libev to help debug problems with
libevent. I would like to support libev and libevent both as options,
so that people can choose the faster, or less buggy library if needed.

An easy way to use libev, without installing it, is to build libev and
give --with-libevent=/home/user/libev-3.51 to configure for unbound.

Best regards,
   Wouter

Beastie wrote:

I hope this is pushed out fairly soon.

Hello,
just wanted to know if there is an (pre-)operational Windows version now that could be used? (I was told end of 2008)
Thank you !
jfc

I see 1.2.0 has been tagged already. What is the hold up with the release?

You can get it from the SVN repository with the following svn command:

  $ svn co http://unbound.nlnetlabs.nl/svn/tags/release-1.2.0/

Regards,

Haw

SVN is not appropriate for my use. I'm also not interesting in having to roll
my own tarball and host it on my own server to workaround deficiencies with
the project.

Hi Brad,

The prerelease of 1.2.0 is done. This is to give package maintainers a
chance to pull things together, make sure packages build right and tell
us if it doesn't. In a day or two (a week or so after the prerelease),
the full release is done. We do this to please the various package
maintainers - because sometimes build scripts change.

This is why it is tagged - a release is upcoming :slight_smile:

Best regards,
   Wouter

Brad wrote: