SYSTEMD-TIMEDATED.SERVICE(8) systemd-timedated.service SYSTEMD-TIMEDATED.SERVICE(8)NAME
systemd-timedated.service, systemd-timedated - Time and date bus mechanism
systemd-timedated is a system service that may be used as a mechanism to change the system clock and timezone, as well as to enable/disable
NTP time synchronization. systemd-timedated is automatically activated on request and terminates itself when it is unused.
The tool timedatectl(1) is a command line client to this service.
See the developer documentation for information about the APIs systemd-timedated provides.
SEE ALSO systemd(1), timedatectl(1), localtime(5), hwclock(8)NOTES
1. developer documentation
systemd 237 SYSTEMD-TIMEDATED.SERVICE(8)
Check Out this Related Man Page
SYSTEMD-TIMESYNCD.SERVICE(8) systemd-timesyncd.service SYSTEMD-TIMESYNCD.SERVICE(8)NAME
systemd-timesyncd.service, systemd-timesyncd - Network Time Synchronization
systemd-timesyncd is a system service that may be used to synchronize the local system clock with a remote Network Time Protocol server. It
also saves the local time to disk every time the clock has been synchronized and uses this to possibly advance the system realtime clock on
subsequent reboots to ensure it monotonically advances even if the system lacks a battery-buffered RTC chip.
The systemd-timesyncd service specifically implements only SNTP. This minimalistic service will set the system clock for large offsets or
slowly adjust it for smaller deltas. More complex use cases are not covered by systemd-timesyncd.
The NTP servers contacted are determined from the global settings in timesyncd.conf(5), the per-link static settings in .network files, and
the per-link dynamic settings received over DHCP. See systemd.network(5) for more details.
timedatectl(1)'s set-ntp command may be used to enable and start, or disable and stop this service.
This file contains the timestamp of the last successful synchronization.
SEE ALSO systemd(1), timesyncd.conf(5), systemd.network(5), systemd-networkd.service(8), timedatectl(1), localtime(5), hwclock(8)systemd 237 SYSTEMD-TIMESYNCD.SERVICE(8)
I am a newbie on the AIX front....I am at present faced with a problem of a service eating up my client's CPU. To be more specific....My client uses backup exec for backing up (v 12.0). The moment I start a backup the beremote.exe (backup exec remote agent for unix, RALUS) service uses... (4 Replies)
hi moring everyone,
i has used systemd-timer running the task, i set every 5 second execute 1 times,but the systemd-timer don't by that also random times execute.
... (2 Replies)
Lucky me, there is this thread or corner, whats on my mind.
As I once complained about systemd, it is in control all over the place, then given an answer about telemetry pings, saying farewell to Debian an still amused how Debian goes into the BSD direction I recently discoverd two or more things... (0 Replies)
Knoppix 8.6 first wide public release to abandon systemd - TechRepublic
I think I will go back to Knoppix. It, along with Debian 6.0.x, were the two most stable OSes I have ever come across... (2 Replies)
I am using the VPN provider Private Internet Access.
I am using the Raspberry Pi 4 with 4GB of RAM, performance on this upgraded board is great.
Anyways I am connecting to its service using systemd's openvpn-client @ US_New_York_City.service
I wonder if I can create a... (5 Replies)