Both of those changes will stop the service from being started, even when the system is rebooted. You don't need to run these commands every time, running them one time will change the system configuration and the service will no longer be started.
On Fri, Apr 17, 2020 at 2:52 AM www <ouyangxua...@163.com> wrote: > > hi Kevin , > > Thank you very much for you help. But how can I save this way of closing time > synchronization by command after system boot up? After I update the system, > the first time I start it, time synchronization is still enabled by default. > It's not appropriate if I close it alone every time. So when I need it start > every time, this function is off. > > > thanks, > Byron > > > > > > At 2020-04-16 18:28:30, "Kevin P. Fleming" <ke...@km6g.us> wrote: > >There is no need to modify systemd. > > > >$ systemctl disable systemd-timesyncd > > > >That command will stop the systemd-timesyncd service from being > >started. It may also be necessary to mask it: > > > >$ systemctl mask systemd-timesyncd > > > >On Thu, Apr 16, 2020 at 6:22 AM www <ouyangxua...@163.com> wrote: > >> > >> Dear all， > >> > >> I want to ask a question，How to modify systemd so that the NTP function is > >> disabled when systemd is first started? > >> > >> The default state of systend is to synchronize time from NTP. We can use > >> timedatectl command to disable NTP synchronize time. But if I flash the > >> system, the NTP synchronize time function will auto enable. so I want > >> modify the systemd and disable NTP synchronize time in default state. > >> > >> thanks, > >> Byron > >> > >> > >> > >> > >> _______________________________________________ > >> systemd-devel mailing list > >> systemd-devel@lists.freedesktop.org > >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
