Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 595
    • Issues 595
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 60
    • Merge requests 60
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #686
Closed
Open
Issue created Jun 21, 2019 by Cathy Almond@cathyaDeveloper

Is it necessary to run the sanity-checker during LFC as well as when starting Kea?

The sanity-checker is (mostly) a useful thing - but (and particularly when the setting is 'warn' as opposed to 'fix'), the amount of logging can be tiresome, especially in a scenario where the output from the checker at startup has been analyzed and it's accepted as something that is known about to be addressed later.

The situation is not going to change, so and option to disable the sanity check during LFC could significantly clean-up the logging output in this scenario.

Whereas, you might want to keep the sanity checker running during LFC if you have set it to 'fix', so that you get to hear about anomalies.

Just a thought..

Support RT #14905 and Support RT #14522

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking