Minor errors on boot

[Mark Andrews]

> On Mon, Oct 22, 2007 at 08:25:15PM +0000, Evan Hunt wrote:
> > 
> > > When my 64-bit Centos5 machine boots up, I see the following messages:
> > > process `rndc' is using obsolete setsockopt SO_BSDCOMPAT
> > > process `named' is using obsolete setsockopt SO_BSDCOMPAT
> 
> Already fixed in BIND >= 9.4.2b1 or in standard CentOS 5 build.
> 
> > 
> > The proper fix would be for the linux people to stop issuing this
> > warning in production kernels.
> 
> Write "something is obsolete" is the best way how tell people that
> some macro is going to be removed.

	No. This sort of warning is for development machines not
	production machines.  As for this particular case removing
	the macro itself would be the way to go as portable code
	(between OS and between Linux releases) already has to
	#ifdef SO_BSDCOMPAT its use.

	There are lots of obsolete calls in all the other OS named
	builds on.  Only Linux see fit to issue a warning on a
	production machine.  This short of thing should be off by
	default.

	Have a look at what we actually had to do to remove the
	warning and that's all inside a #ifdef SO_BSDCOMPAT.
	It's ridiculous to expect every application that needs
	to be portable to do that sort of thing.

	Note:  We can't actually remove the setsockopt altogether
	as it is required for some kernels.  New applications can
	ignore old OS's.  Old applications however need to keep
	running on the old OS's.

	Mark
 
> Adam
> 
> -- 
> Adam Tkac, Red Hat, Inc.
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org