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 594
    • Issues 594
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 58
    • Merge requests 58
  • 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
  • #2203
Closed
Open
Issue created Nov 23, 2021 by Francis Dupont@fdupontDeveloper

Update doc about ways to get the config/build report

There are 2 or 3 ways to get the config/build report when the config.report file itself is not available:

  • the -W command line argument
  • a grep for ';;;;' on the extracted strings from the main binary
  • when there is a control channel the build-report command

All have different constraints: the first requires to run the binary, the second is more hairy but requires only access to the main binary, and the last requires a running binary but can be done remotely.

Unfortunately it seems this is not explained in the ARM for all Kea commands compiled from C++ so:

  • the ARM must be updated
  • each way should be checked (some failures were reported and fixed so do not assume they work)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking