问题原文
原帖链接 · OrangeDog · CC BY-SA 4.0
I have some Ubuntu 18.04.1 servers. They all show this service being started rougly every 10 minutes.
Jan 7 06:29:05 csrf-prod1-vm dbus-daemon[434]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.12841' (uid=0 pid=25418 comm="timedatectl " label="unconfined")
Jan 7 06:29:05 csrf-prod1-vm systemd[1]: Starting Time & Date Service...
Jan 7 06:29:05 csrf-prod1-vm dbus-daemon[434]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jan 7 06:29:05 csrf-prod1-vm systemd[1]: Started Time & Date Service.
Perhaps of note is I have configured timesyncd with some network-local ntp servers.
$ timedatectl status
Local time: Mon 2019-01-07 18:15:54 UTC
Universal time: Mon 2019-01-07 18:15:54 UTC
RTC time: Mon 2019-01-07 18:15:55
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
It appears that this service just starts systemd-timedated. Is this what's used by systemd-timesyncd in order to set the time? Why does it not stay running as the suffix d[aemon] would suggest? Or is it redundant to systemd-timesyncd and should be disabled in some way?
已采纳解答
原帖链接 · OrangeDog · CC BY-SA 4.0
It turns out that a configuration management system was calling timedatectl every ~10 minutes in order to check the current timezone.
This calls timedate1 over DBUS to get the answer, which only activates on incoming messages.
So entirely normal, and entirely my fault.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
