Subject: bug#76401: ntpd segfaults when started too early

From: Ludovic Courtès <[email-masked]>
Date: Tue, 18 Feb 2025 19:23:38 +0100

Hi,

I noticed that ntpd segfaults when started “too early”, presumably
before networking is up:

--8<---------------cut here---------------start------------->8---
ludo@bayfront ~$ sudo herd status ntpd
● Status of ntpd:
  It is stopped since 07:19:58 PM (110 seconds ago).
  Process terminated with signal 11.
  It is disabled.
  Provides: ntpd
  Requires: user-processes networking
  Custom action: configuration
  Will be respawned.
  Last respawned on 07:19:58 PM (110 seconds ago).
  Latest exits:
    - 2025-02-18 19:19:58  Process terminated with signal 11.
    - 2025-02-18 19:19:58  Process terminated with signal 11.
    - 2025-02-18 19:19:58  Process terminated with signal 11.
    - 2025-02-18 19:19:57  Process terminated with signal 11.
    - 2025-02-18 19:19:57  Process terminated with signal 11.
ludo@bayfront ~$ guix system describe
Generation 1210 Feb 18 2025 15:26:24    (current)
  file name: /var/guix/profiles/system-1210-link
  canonical file name: /gnu/store/yqw5xzxl4d3da10dim33p5nxn1gy17i9-system
  label: GNU with Linux-Libre 5.10.234
  bootloader: grub
  root device: /dev/md0
  kernel: /gnu/store/04g6ij7nqmk4mqxrqd9zq31bm8fysslf-linux-libre-5.10.234/bzImage
  channels:
    guix:
      repository URL: https://git.savannah.gnu.org/git/guix.git
      branch: master
      commit: 96fe9adf54772e0824e098a6a089306a75101218
  configuration file: /gnu/store/12d2fsn80fwwsmapp3m3pxbfd3q4pra8-configuration.scm
--8<---------------cut here---------------end--------------->8---

(Seen on several different machines.)

Ludo’.