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 522
    • Issues 522
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • 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
  • #1796

Closed
Open
Created Apr 27, 2020 by Timothe Litt@tlhackque

Log files should not be closed until their successor is open.

From #1042 (closed) as requested by @ondrej :

Identifying and debugging this would be much simpler if named ensured that all errors are logged by changing logging such that a log file isn't closed until its successor is open (assuming my guess is correct). This would guarantee that a failure to open gets logged in the previous logfile, which could continue to log. I have verified that the current logging code closes files before opening a successor

The quote is 11 months old - I haven't re-verified the observation in current code as I'm seriously underwater at the moment.

Assignee
Assign to
Time tracking