Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!newsfeed.direct.ca!portc01.blue.aol.com!news-res.gsl.net!news.gsl.net!news-peer.gsl.net!news.gsl.net!swrinde!howland.erols.net!newsfeed.internetmci.com!in3.uu.net!news.gtn.com!klicman.de!ora.de!bad From: bad@ora.de (Christoph Badura) Subject: Re: bind problems and installation Message-ID: <Dx9vy7.IMp@ora.de> Organization: O'Reilly/International Thomson Verlag References: <322E9CAF.41C67EA6@corpex.com> Date: Thu, 5 Sep 1996 18:42:07 GMT Lines: 15 In <322E9CAF.41C67EA6@corpex.com> Neil <neil@corpex.com> writes: >However I thought I'd ask whether FreeBSD bind suffered the same failure >as Sun bind. When ifconfig is used to allocate multiple IP's to the >same machine, bind will not restart if there are more than 64 IP's >allocated. Hence to restart bind, the machine must be restarted. Currently, BIND has this problem on all machines. This is because it binds a socket to the address of every running interface of the machine. Each of these sockets uses up a file descriptor. The limit on open file descriptors is 64/256 on SunOS. I believe it is higher by default on FreeBSD. In anycase you could raise the limit for bind. -- Christoph Badura O'Reilly/International Thomson Verlag