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 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • 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
  • #1724

Closed
Open
Created Apr 02, 2020 by Michał Kępień@michalOwner0 of 2 tasks completed0/2 tasks

Revise installation locations for certain BIND binaries

The following discussion from !985 (merged) should be addressed:

  • @michal started a discussion: (+2 comments)

    Here is an exhaustive list of binaries which are currently installed into ${sbindir} that this MR causes to be installed into ${bindir}:

    • ddns-confgen
    • named-checkconf
    • named-checkzone
    • named-journalprint
    • named-nzd2nzf
    • nsec3hash
    • rndc-confgen
  • @ondrej said:

    BTW it's wrong to install these to sbin, as they don't require administrator privileges to run.

Assignee
Assign to
Time tracking