Date: Thu, 26 Jan 2012 22:48:36 +0100 From: Marcin Wisnicki <mwisnicki+freebsd@gmail.com> To: dougb@freebsd.org Cc: freebsd-bugs@freebsd.org Subject: Re: bin/158543: named(8) spams logs with unexpected errors Message-ID: <CAC9GOO_zrZ-bryYr1hp9EdHzJrOs15XqobQzsL3DqFhjyRnhUw@mail.gmail.com> In-Reply-To: <201201250258.q0P2wnsl066283@freefall.freebsd.org> References: <201201250258.q0P2wnsl066283@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 25, 2012 at 03:58, <dougb@freebsd.org> wrote: > Synopsis: named(8) spams logs with unexpected errors > > named is telling you that the network is down, so it cannot > do its job. If you don't want this to happen, disable it > before you go off line (e.g., service named stop). > Do you really think it's acceptable for named to fatally break the machine (necessitating manual repair) or at minimum make logs useless if it cannot contact root servers ??? And no, I don't go offline. There are many reasons beyond my control why connectivity might not work. Also it happens at every startup because named starts while ppp is still establishing connection.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC9GOO_zrZ-bryYr1hp9EdHzJrOs15XqobQzsL3DqFhjyRnhUw>