Re: Disable log message

[Novosielski, Ryan]

While I can see maybe not being interested, caring enough to supress it has me curious.



----- Original Message -----
From: Alan Clegg [mailto:al...@clegg.com]
Sent: Friday, October 19, 2012 06:13 PM
To: bind-...@isc.org <bind-...@isc.org>
Subject: Re: Disable log message


On Oct 18, 2012, at 1:13 PM, Chris Thompson <ce...@cam.ac.uk> wrote:

> On Oct 18 2012, Jeremy C. Reed wrote:
>
>> On Thu, 18 Oct 2012, Jack Tavares wrote:
>>
>>> I am running bind9.8.x built from source and I see this message in the logs
>>> built with '--prefix=/blah' '--sbindir=/blah' '--sysconfdir=/blah' '--localstatedir=/var' '--exec-prefix=/usr' '--libdir=/usr/lib' '--mandir=/usr/share/man' '--with-openssl=/blah' '--enable-fixed-rrset' '--enable-shared' '--enable-threads' '--enable-ipv6' '--with-libtool' etc etc etc I would prefer to not have that show up in the log.
>>> Short of modifying the source, is there an easy way to disable that?
>>
>> No way to disable just it. It is in the "general" catch-all category.
>
> Also, it is output before the configuration "logging" directives have been
> processed, so it comes out with the internal defaults for category and
> priority (daemon.notice). Any suppression would need to be done at the
> syslog level.
>
> But I have some difficulty understanding why anyone would want it suppressed.
> It's true that BIND is a bit noisier than it used to be at this stage, but
> can this really be a problem? Do you let the black hats see your system logs?


This message was added by general recognition that being able to rebuild a "drop-in" binary for BIND when you didn't have access to the build directory (where the config.log contains the information) was a good thing.

I, for one, see no reason to suppress this message (but I do have blind spots at times).

AlanC
--
Alan Clegg | +1-919-355-8851 | al...@clegg.com

[Warren Kumari]

On Oct 19, 2012, at 6:13 PM, Alan Clegg <al...@clegg.com> wrote:

>
> On Oct 18, 2012, at 1:13 PM, Chris Thompson <ce...@cam.ac.uk> wrote:
>
>> On Oct 18 2012, Jeremy C. Reed wrote:
>>
>>> On Thu, 18 Oct 2012, Jack Tavares wrote:
>>>
>>>> I am running bind9.8.x built from source and I see this message in the logs
>>>> built with '--prefix=/blah' '--sbindir=/blah' '--sysconfdir=/blah' '--localstatedir=/var' '--exec-prefix=/usr' '--libdir=/usr/lib' '--mandir=/usr/share/man' '--with-openssl=/blah' '--enable-fixed-rrset' '--enable-shared' '--enable-threads' '--enable-ipv6' '--with-libtool' etc etc etc I would prefer to not have that show up in the log.
>>>> Short of modifying the source, is there an easy way to disable that?
>>>
>>> No way to disable just it. It is in the "general" catch-all category.
>>
>> Also, it is output before the configuration "logging" directives have been
>> processed, so it comes out with the internal defaults for category and
>> priority (daemon.notice). Any suppression would need to be done at the
>> syslog level.
>>
>> But I have some difficulty understanding why anyone would want it suppressed.
>> It's true that BIND is a bit noisier than it used to be at this stage, but
>> can this really be a problem? Do you let the black hats see your system logs?
>
>
> This message was added by general recognition that being able to rebuild a "drop-in" binary for BIND when you didn't have access to the build directory (where the config.log contains the information) was a good thing.

Yah, a very good thing… This has been really really useful to me on a number of occasions…

>
> I, for one, see no reason to suppress this message (but I do have blind spots at times).

Me neither, but I am interested why folk might want to…

W

>
> AlanC
> --
> Alan Clegg | +1-919-355-8851 | al...@clegg.com
>
>
>
>
>

> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
>
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

--
Consider orang-utans.
In all the worlds graced by their presence, it is suspected that they can talk but choose not to do so in case humans put them to work, possibly in the television industry. In fact they can talk. It's just that they talk in Orang-utan. Humans are only capable of listening in Bewilderment.
-- Terry Practhett

[Michael Hoskins (michoski)]

-----Original Message-----

From: Warren Kumari <war...@kumari.net>
Date: Friday, October 19, 2012 8:56 PM
To: Alan Clegg <al...@clegg.com>
Cc: "bind-...@isc.org" <bind-...@isc.org>
Subject: Re: Disable log message

>

>Yah, a very good thingŠ This has been really really useful to me on a
>number of occasionsŠ

>
>>
>> I, for one, see no reason to suppress this message (but I do have blind
>>spots at times).
>

>Me neither, but I am interested why folk might want toŠ

Maybe it's viewed as information disclosure? It's always good to give
folks a choice -- what's useful for some (or others, like me, don't care
about at all) will be annoying to others.

[Warren Kumari]

Ah, that's a good point, especially if BIND is being incorporated into an appliance / black box and there is no need for the users of the appliance to know what all goes on under the hood?

W

> It's always good to give
> folks a choice -- what's useful for some (or others, like me, don't care
> about at all) will be annoying to others.
>

--
"Go on, prove me wrong. Destroy the fabric of the universe. See if I care." -- Terry Prachett

[Chris Buxton]

An an employee of the maker of an appliance solution, I can say that we gladly tell our customers what's going on under the hood. If we didn't, they wouldn't trust us.

Chris Buxton
BlueCat Networks

[David Miller]

Does this log message provide any information that the -V option doesn't
provide?

$ named -V
BIND 9.8.0-P4 built with '--prefix=/blah' '--exec-prefix=/blah'
'--enable-threads' '--enable-ipv6' 'CFLAGS=-O2 -march=native ...and so on...
using OpenSSL version: OpenSSL 1.0.0d 8 Feb 2011
using libxml2 version: 2.7.8

-DMM

[Warren Kumari]

Nope, but there is a difference between someone actually being interested and looking (or asking their vendor) and having it show up directly in the logs… Someone who cares will be able to quite easily tell that it is BIND (esp if they get something like console access), but I have seem some appliance folk who don't *really* publicize this…

W

>
> -DMM

> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
>
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>

--

"He who laughs last, thinks slowest."
-- Anonymous

[Chris Thompson]

On Oct 20 2012, David Miller wrote:

[...]

>Does this log message provide any information that the -V option doesn't
>provide?

Given the number of times that problems brought up on this list turn out
to be due to people not actually running the named binary they thought
they were running, the more that the actually executing named says about
itself, the better.

--
Chris Thompson
Email: ce...@cam.ac.uk

[Jack Tavares]

I wasn't suggesting that it be removed.

I was asking if it was possible to disable it if desired.
The answer is obviously no.

Thank you all for your time.
--
Jack Tavares
"How many more can we sell with this button?"
________________________________________
From: bind-users-bounces+j.tavares=f5....@lists.isc.org [bind-users-bounces+j.tavares=f5....@lists.isc.org] on behalf of Chris Thompson [ce...@cam.ac.uk]
Sent: Sunday, October 21, 2012 14:58
To: bind-...@lists.isc.org

Subject: Re: Disable log message

On Oct 20 2012, David Miller wrote:

[Novosielski, Ryan]

I think many of us were just curious why someone would even think to disable it. Would be great if you could indulge (maybe something we've not thought of).

[Tony Finch]

Alan Clegg <al...@clegg.com> wrote:
>
> This message was added by general recognition that being able to rebuild
> a "drop-in" binary for BIND when you didn't have access to the build
> directory (where the config.log contains the information) was a good
> thing.
>

> I, for one, see no reason to suppress this message (but I do have blind
> spots at times).

I have a tangentially related patch. I wanted to direct BIND's startup
logging to the same file that it is configured to use after initialization -
rather than always sending startup messages to syslog. The patch adds a -L
command-line option for this purpose. You could use it to suppress the
startup logging with -L/dev/null I suppose...

http://dotat.at/cgi/git/bind-9.git?a=commitdiff;h=logging-startup

Tony.
--
f.anthony.n.finch <d...@dotat.at> http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.