timedatectl reports wrong status for timesyncd in core18
@valentindavid is already working on this.
Since Apr 8, 2024.
- Dominant language
- Shell
- Stars
- 14
- Forks
- 27
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Description
when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
systemd-timesyncd.service ...
sadly it does report it wrongly (the tool reports it inactive while the service is actually running):
```
ogra@pi4:~$ timedatectl
Local time: Wed 2020-07-01 10:52:48 UTC
Universal time: Wed 2020-07-01 10:52:48 UTC
RTC time: n/a
Time zone: n/a (UTC, +0000)
System clock synchronized: yes
systemd-timesyncd.service active: no
RTC in local TZ: no
ogra@pi4:~$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 779 (systemd-timesyn)
Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─779 /lib/systemd/systemd-timesyncd
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.