Upstream software project

chrony

Empty pool preconfiguration for chrony

About chrony

Empty pool preconfiguration for chrony

This project links 5 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; openSUSE Leap 15.6: 4 package records. Catalog coverage diagram, not an application screenshot.chrony: recorded package coverageDebian 12 (Bookworm)1 recordsopenSUSE Leap 15.64 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
chrony
Publisher
Not authoritatively mapped
Native package records
5
Operating systems
debian-12, opensuse-leap-15-6
License expression
GPL-2.0-only
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Chrony is an implementation of the Network Time Protocol (NTP). It can synchronize the system clock with NTP servers, reference clocks (e.g. a GPS receiver), and manual input using wristwatch and keyboard. It can also operate as an NTPv4 (RFC 5905) server and peer to provide a time service to other computers in the network. Chrony consists of two programs: chronyd and chronyc. Chronyd is a daemon which runs in the background on the system. It obtains measurements of the system clock’s offset relative to time servers on other systems via the network and adjusts the system time accordingly. For isolated systems, the user can periodically enter the correct time by hand (using chronyc). In either case, chronyd determines the rate at which the computer gains or loses time, and compensates for this. Chronyd can act as either a client or a server. Chronyc provides a user interface to chronyd for monitoring its performance and configuring various settings. It can do so while running on the same computer as the chronyd instance it is controlling or a different computer.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package chrony

    bookworm (Debian 12 (Bookworm)) (net): Versatile implementation of the Network Time Protocol

    4.3-2+deb12u3: amd64 arm64

openSUSE Leap 15.6

  1. Package chrony

    leap-15.6 (openSUSE Leap 15.6) (Productivity/Networking/Other): System Clock Synchronization Client and Server

    4.1-150400.19.4: aarch64 ppc64le s390x x86_64

    Source: chrony

  2. Package chrony-pool-empty

    leap-15.6 (openSUSE Leap 15.6) (Productivity/Networking/Other): Empty pool preconfiguration for chrony

    4.1-150400.19.4: noarch

    Source: chrony

  3. Package chrony-pool-openSUSE

    leap-15.6 (openSUSE Leap 15.6) (Productivity/Networking/Other): Chrony preconfiguration for openSUSE

    4.1-150400.19.4: noarch

    Source: chrony

  4. Package chrony-pool-suse

    leap-15.6 (openSUSE Leap 15.6) (Productivity/Networking/Other): Chrony preconfiguration for SUSE

    4.1-150400.19.4: noarch

    Source: chrony

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.