A policy for removing named.conf options.

[Lightner, Jeffrey]

Systemd writes logs for things it starts to the Journal which can be viewed with journalctl command.

On some distros (e.g. RHEL7) it also continues to write many things to system logs like /var/log/messages.   Not all of what goes to the Journal is in /var/log/messages but all of what is in /var/log/messages goes to the Journal.


From: bind-users <bind-users-bounces at lists.isc.org> On Behalf Of Leroy Tennison
Sent: Thursday, June 13, 2019 9:57 AM
To: bind-users at lists.isc.org
Subject: Re: A policy for removing named.conf options.


First of all, I appreciate the fact that you are seeking feedback before acting, thank you.



I agree with Warren's point about logs and, unfortunately, also with his analysis concerning distributions.  A couple of additional comments.



The major Linux distributions are moving to systemd (whether we like it or not), whatever is done has to take that into account.

The only thing you have (the most) control over is the software you produce, another approach would be to add a generic message facility to all your utilities that, for example, displays the contents of a file at startup (if it exists).  Daemon startup could check the configuration files and generate the content of the displayed file ("You're using 'blah' option which is depreciated, see http://...").  This way, if an administrator uses any of your utilities, they see the message.  For "extra credit", add a "don't display this message again" option.  If an administrator manages to support your software without using any of your utilities then they are capable of remediating their own problems.

Harriscomputer

Leroy Tennison
Network Information/Cyber Security Specialist
E: leroy at datavoiceint.com<mailto:leroy at datavoiceint.com>

[cid:image001.png at 01D521D3.3503B870]

2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com<http://www..com>


This message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc. These companies are listed here<http://subscribe.harriscomputer.com/>.

If you prefer not to be contacted by Harris Operating Group please notify us<http://subscribe.harriscomputer.com/>.



This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.



________________________________
From: bind-users <bind-users-bounces at lists.isc.org<mailto:bind-users-bounces at lists.isc.org>> on behalf of Ondřej Surý <ondrej at isc.org<mailto:ondrej at isc.org>>
Sent: Thursday, June 13, 2019 8:37 AM
To: Warren Kumari
Cc: bind-users at lists.isc.org<mailto:bind-users at lists.isc.org>
Subject: [EXTERNAL] Re: A policy for removing named.conf options.

Hi Warren and everybody,

first, let me thank for the fruitful discussion!

> On 13 Jun 2019, at 15:18, Warren Kumari <warren at kumari.net<mailto:warren at kumari.net>> wrote:
>
> Many many people don't look at their logs -- could named also print
> stuff to (stdout, stderr) when starting?
>
> Note that this will require some testing -- various distributions use
> various init scripts - in many cases things printed at startup don't
> actually make it to the console, and I'm suspecting some init systems
> will barf, but...

It's undermentioned in the policy proposal, but the named-checkconf
will be loud about the deprecated options.  We can then bug distros to
integrate the named-checkconf run into the pre/postinst maintainer scripts.
(Hey myself, fix the Debian package. Ok, myself...)

> Another phased approach would be to require users to acknowledge that
> the feature is being deprecated -- initially it could warn, and then
> named could require command line flags to enable the (being)
> deprecated features, and then in the next release they would stop (e.g
> named --enable_deprecated_cleaning-interval). I think that this is way
> overkill, but just a thought.

That would take 4 full years to deprecate single option, as we need to take
people that upgrade from ESV to ESV into account, and we were aiming
at slightly "faster" approach :-).

Thanks,
--
Ondřej Surý
ondrej at isc.org<mailto:ondrej at isc.org>

_______________________________________________
Please visit https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.isc.org%2fmailman%2flistinfo%2fbind-users&c=E,1,yw6EFdI2bCuC2na2ur7-F1G92uow3vtsWpruIMf4wVLkS96WojpFuQ9yFBatKWXzbsJWnOpPiH9CsJum226CS7Pr4Oi5GsbAuvBcrpl8GbMNpGxrMrpl3M9XNfw,&typo=1 to unsubscribe from this list

bind-users mailing list
bind-users at lists.isc.org<mailto:bind-users at lists.isc.org>
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.isc.org%2fmailman%2flistinfo%2fbind-users&c=E,1,YVga50vu8jtaQRjJyL3EYLTif7UroYK4D1uIX3KMLr4tHA0WEL7m4ytBOAe3Ry1gkCjeaIlSnMv7JrNAOoVnw5JLA1CytXg871RJx0Ey&typo=1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20190613/d5fc2f43/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8276 bytes
Desc: image001.png
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20190613/d5fc2f43/attachment-0001.png>