Milter-greylist

nm : libbind.so.4.0.2 : no symbols   :(

libbind.so.4.0.2 is part of bind-libs-9.3.2-20.FC5

Searching the system reveals only this libbind.so.4.0.2 (and the 
symbolic link to it), reinstall of bind-libs-9.3.2-20.FC5 results in 
the same file being created.
I went ahead and downloaded

Downloaded the latest development
bind-libs-9.3.2-41.fc6.i386.rpm
bind-utils-9.3.2-41.fc6.i386.rpm
then rpm -U bind-util* bind-libs*

New file is created Sep 11th, 2006, (libbind.so.4.0.2)
Same Symbol Results (nm: libbind.so.4.0.2: no symbols)

Obviously this is a Bind 9.3.2-41 file so it has to be thread safe.

Database size is 40 megs now (greylist.db)
System stable after 24 hours with DNSRBL disabled in greylist.conf, 
no MX Sync.

All your comments have been appreciative!  Would love to implement 
DNSRBL if it can be stable on Fedora Core 5 / 6


--- In milter-greylist@yahoogroups.com, manu@... wrote:
>
> Brian J. Lewis <brianlewis@...> wrote:
> 
> > It did, there is only one libbind.so.4 (actually a symbolic link 
to 
> > libbind.so.4.0.2) in /usr/lib/ and LDD shows that this is where 
its 
> > linked.  libbind.so is also a symbolic link to the same file as 
well.
> > These are from Bind 9.3.2 which is thread safe.
> (snip)
> >  libbind.so.4 => /usr/lib/libbind.so.4 (0x00d2e000)
> 
> Are you sure that one is from BIND9? Please run 
> nm /usr/lib/libbind.so.4| grep res_ninit 
> 
> > I recompiled without DNSRBL and removed the DNSRBL lines in 
> > greylist.conf and the servers have been stable!  In fact I only 
> > recompiled on one server, the other 3 servers I just removed the 
> > lines from greylist.conf and restarted Milter-Greylist and they 
are 
> > stable as well, so there seems to be a bug in Milter-Greylist 
when 
> > compiled on Fedora Core 5 or 6 with Bind 9.3.x that causes 
> > instability under high load (2000-3000 messages rejected per hour)
> 
> That smells like thread insafety..
> 
> -- 
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz
> manu@...
>