Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Turris OS packages Turris OS packages
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Turris
  • Turris OS
  • Turris OS packagesTurris OS packages
  • Issues
  • #772

Closed
Open
Created Jun 16, 2021 by Karel Koci@kkoci🤘Owner

Run resolver with higher priority

DNS is a sensitive service and it should take priority over most other services running on the router as it is one of the primary services it provides. The solution is to run it the same way as for example ntpd with lower niceness. I would suggest -5.

From my tests, this solves issues when an update fails because of failed resolving (updater-lists#1 (moved)).

It should be enough to add procd_set_param nice '-5' to the init script in an appropriate location.

Assignee
Assign to
Time tracking