> >
> >Feb 26 21:36:40 ns1 kernel: process `named' is
> using obsolete setsockopt 
> >SO_BSDCOMPAT
> >Feb 26 21:38:09 ns1 kernel: process `dig' is using
> obsolete setsockopt 
> >SO_BSDCOMPAT
> 
> SO_BSDCOMPAT is enabling bsd bug-to-bug
> compatability socket option... this 
> is used by the udp protocol module in linux 2.0 and
> 2.2... in later kernel 
> versions... support for this socket option has been
> phased out... linux 2.4 
> silently ignores it while linux 2.6 generates a
> kernel warning (by calling 
> printk() function call) if a program uses this
> option as what you have seen 
> above...
> 
> bind was developed under BSD environment and bind
> developers still uses this 
> because they have customers that have kernels that
> require SO_BSDCOMPAT to 
> operate... therefore they cannot remove the
> setsockopt(SO_BSDCOMPAT) call...
> 
> for linux... you have to undefine the #define
> SO_BSDCOMPAT at 
> lib/isc/unix/socket.c by putting #undef SO_BSDCOMPAT
> after the #include 
> lines or whatever method as long as SO_BSDCOMPAT is
> undefine...
> 
> fooler.
> 
hi guys,
just finished reinstalling bind 9.4.0. strange thing
is whenever i put it behind a firewall it slows down
query process =( ... do i have to put some config on
my firewall or even change some query port on my bind
?
im using cp firewall...

tnx


                            JCB 
    Registered Linux User #371834
  http://counter.li.org
   

















 
____________________________________________________________________________________
Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to