BIND 10 #1890: CFGMGR_RENAMED_CONFIG_FILE misleading
BIND 10 Development
do-not-reply at isc.org
Wed May 30 06:09:01 UTC 2012
#1890: CFGMGR_RENAMED_CONFIG_FILE misleading
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: jreed
Type: | Status: reviewing
defect | Milestone:
Priority: | Sprint-20120612
medium | Resolution:
Component: Boss | Sensitive: 0
of BIND | Sub-Project: Core
Keywords: | Estimated Difficulty: 2
Defect Severity: Low | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by muks):
Replying to [comment:5 jreed]:
> It makes the admin think that the configuration was renamed and that
they should consider using the new name.
Now I follow what you meant in the description :)
> The "will create" make admin think it may happen then or soon, but
really it will never happen until something tells it to create a new
configuration.
>
> I think some may choose to not log INFO. WARNING may be useful for other
admins to know this happened.
The clear-config action currently only happens if it is requested by an
admin. I agree it should be logged visibly if it happens automatically,
but WARNING is something that should be to warn the admin (of impending
error/failure situations), not as a notice. The closest level we have
right now for this message is INFO.
Maybe we can introduce a NOTICE level for such messages. Let's talk about
it in the bi-weekly call.
>
> (In other words, my thoughts never changed on why I opened the ticket.)
--
Ticket URL: <http://bind10.isc.org/ticket/1890#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list