Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • alpine-conf alpine-conf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpine
  • alpine-confalpine-conf
  • Issues
  • #10522
Closed
Open
Created Jun 30, 2022 by Daniel F. Dickinson@danielfdickinson

Example NTPOPTS generated by setup-alpine fails to automate client selection

For 3.16.0 (and earlier), the NTPOPTS example for the answer file generated by setup-alpine at https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-alpine.in#L116 fails to let setup-alpine automatically configure the NTP client. (That is one is still prompted to choose an NTP client). It was pointed out on the devel mailing list[1] that this is likely due to setup-ntp having -c for getopts but the setting of resp using the first positional parameter whether or not -c is used.

The initial thought was to change setup-ntp but it occurs to me that has more potential to go wrong than updating the example answers file in setup-alpine and the docs https://gitlab.alpinelinux.org/alpine/docs/user-handbook/-/blob/master/modules/Installing/examples/setup_example.sh to use (after of course verifying (something I intend to do) that NTPOPTS="openntpd" (or NTPOPTS="chrony" would work as expected).

EDIT: This is only an issue for non-Qemu machines; Qemu machines use kvm-clock and thus the scripts skip setting up an NTP server for them.

Which solution is preferred by the dev team?

[1] https://lists.alpinelinux.org/~alpine/devel/%3C4caa8c5f-7ebf-ad2f-0e92-29428785fe60%40wildtechgarden.ca%3E#%3CYr1TRebPEJ/SfWoG@codewreck.org%3E

Edited Jul 01, 2022 by Daniel F. Dickinson
Assignee
Assign to
Time tracking