Installing the NTP Daemon?

Hi everyone,
I am trying to install the NTP Daemon using these instructions but this is the response I am getting:

$ sudo dnf install ntp
balena-etcher 661 B/s | 648 B 00:00
balena-etcher-noarch 723 B/s | 648 B 00:00
balena-etcher-source 714 B/s | 648 B 00:00
keybase 7.4 kB/s | 3.3 kB 00:00
No match for argument: ntp
Error: Unable to find a match: ntp

1 Like

The ntp package has been obsoleted by ntpsec from the looks of it:

Could you please open a ticket about the outdated docs page? You can click the “bug” icon in the top right hand corner to file one.


I don’t know why you feel you need ntp.
The system installs software for that purpose (part of the systemd services) and automatically keeps time synced without adding additional packages.

Otherwise the post by Ankur seems correct.

I am trying out Lynis suggestions that I got.
These ones :

Suggestions (29):

  * Consider hardening system services [BOOT-5264] 
    - Details  : Run '/usr/bin/systemd-analyze security SERVICE' for each service

  * If not required, consider explicit disabling of core dump in /etc/security/limits.conf file [KRNL-5820]

  * Check PAM configuration, add rounds if applicable and expire passwords to encrypt with new values [AUTH-9229]

  * Configure password hashing rounds in /etc/login.defs [AUTH-9230]

  * When possible set expire dates for all password protected accounts [AUTH-9282]

  * Look at the locked accounts and consider removing them [AUTH-9284]

  * Default umask in /etc/login.defs could be more strict like 027 [AUTH-9328]

  * To decrease the impact of a full /var file system, place /var on a separate partition [FILE-6310]

  * The database required for 'locate' could not be found. Run 'updatedb' or 'locate.updatedb' to create this file. [FILE-6410]

  * Check DNS configuration for the dns domain name [NAME-4028]

  * Add the IP name and FQDN to /etc/hosts for proper name resolving [NAME-4404]

  * Install debsums utility for the verification of packages with known good database. [PKGS-7370]

  * Determine if protocol 'dccp' is really needed on this system [NETW-3200]

  * Determine if protocol 'sctp' is really needed on this system [NETW-3200]

  * Determine if protocol 'rds' is really needed on this system [NETW-3200]

  * Check iptables rules to see which rules are currently not used [FIRE-4513]

  * Install Apache mod_evasive to guard webserver against DoS/brute force attempts [HTTP-6640]

  * Install Apache modsecurity to guard webserver against web application attacks [HTTP-6643]

  * Enable logging to an external logging host for archiving purposes and additional protection [LOGG-2154]

  * Check what deleted files are still in use and why. [LOGG-2190]

  * Add a legal banner to /etc/issue, to warn unauthorized users [BANN-7126]

  * Add legal banner to /etc/, to warn unauthorized users [BANN-7130]

  * Enable sysstat to collect accounting (no results) [ACCT-9626]

  * Use NTP daemon or NTP client to prevent time issues. [TIME-3104]

  * Check available certificates for expiration [CRYP-7902]

  * Determine if automation tools are present for system management [TOOL-5002]

  * Consider restricting file permissions [FILE-7524] 
    - Details  : See screen output or log file
    - Solution : Use chmod to change file permissions

  * One or more sysctl values differ from the scan profile and could be tweaked [KRNL-6000] 
    - Solution : Change sysctl value or disable test (skip-test=KRNL-6000:<sysctl-key>)

  * Harden compilers like restricting access to root user only [HRDN-7222]

This is mostly superceded by the systemd management of time, and is related to issues that might occur with the system time out of sync with UTC. Systemd manages keeping things in sync.

Remember always that there are usually many different ways to perform the same task and verify if that suggestion applies to your system. With systemd control of time ntpd is not required.

In an enterprise that isolates its internal systems from the internet, ntpd and an internal NTP server may be needed to sync time within all systems on the LAN. With home systems and having direct internet access time is easily managed differently.

Evaluate each of those based on your own use case and do not always assume they apply to you.