[3287] in testers

home help back first fref pref prev next nref lref last post

Re: named in sun 8.1 is noisy

daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jun 23 14:14:43 1997

To: Jonathon Weiss <jweiss@MIT.EDU>
Cc: Greg Hudson <ghudson@MIT.EDU>, danw@MIT.EDU (Dan Winship), testers@MIT.EDU
In-Reply-To: Your message of "Mon, 23 Jun 1997 14:08:40 EDT."
             <199706231808.OAA00379@livas440.wwnet.com> 
Date: Mon, 23 Jun 1997 14:14:36 EDT
From: Greg Hudson <ghudson@MIT.EDU>

> > > It looks like bind 4.9.3 (which solaris 2.5.1 uses) does an openlog
> > > with LOG_CONS. The openlog manpage implies that this only causes it
> > > to write to the console if it can't write to syslogd

> > I believe that actually functions correctly; I see named warning
> > messages at boot time which I don't see if I restart named after
> > syslogd is running.

> I believe that Dan was complaining that the "only" was not being
> honored.

I understood that.  At boot time, named cannot write to syslogd, so it
displays messages (logged at daemon.info, I believe) on the console.
If I restart named later, the messages do not go go the console.
Thus, I am led to believe that the "only" clause is being honored.

> I ihave a similar probelm except that I get zephyred the message,
> and it appears in my console.  I'm using the athenizd syslogd with
> an athena default syslog.conf, plus

If the default athena syslog.conf file logs the message to your
console, adding a line to it isn't going to make it less likely to
appear in your console.  I'm not sure why you and Dan brought up this
detail; I get the impression that I'm missing something.

home help back first fref pref prev next nref lref last post