Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 527
    • Issues 527
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #3064

Closed
Open
Created Dec 20, 2021 by Artem Boldariev@artemOwner

Disable the interface-interval timer on systems where route/netlink messages work

This issue is essentially a follow-up from #3059 and !5638 (merged).

The idea is that there is no point in having interface-interval on the systems where a kernel reliably informs us about the state of network interfaces. On such systems, having interface-interval is redundant. At the very least the list of such systems includes all Linux distributions, where NetLink messages are available for that.

We may wish to disable the timer with a WARNING message in the log earlier during 9.19 release series to see how well it will work on practice (it should work just fine, IMO).

Assignee
Assign to
Time tracking