Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 631
    • Issues 631
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 104
    • Merge Requests 104
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #737

Closed
Open
Opened Nov 23, 2018 by Ondřej Surý@ondrejOwner

Uniquely number and document emitted log messages

Cathy Almond @cathya wrote:

Can we, off the back of this, take a look at the Kea model for uniquely numbering and documenting emitted logged messages and open a feature request for doing something similar in BIND?

Brian Conry wrote:

I've had it on my personal wish-todo-list to figure out how to generate the catalog files as part of a make operation, ever since I had to troubleshoot a problem with the text start typing instead of out of memory because the OS vendor had pre-installed catalog files that that matched their build of BIND.

But eliminating the (almost completely) unused catalog functionality would work too.

Actually, doing the "unique numbering" thing seems to me like it would be a helpful step if we were to try to preserve support for catalog files, so it seems to me to be something that we should do regardless.

Assignee
Assign to
Long-term
Milestone
Long-term
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#737