No, but I have now run 'timedatectl set-ntp 0' and ntpd is still running after a reboot.There also does not seem to be anything ntp related in '/etc/systemd/system/':$ grep -r ntp /etc/systemd/system
Things should be working as outlined in the wiki: https://wiki.archlinux.org/index.php/Sy … managementIf you think it's important, you can add a line about halt, although it's already mentioned in systemd FAQ https://wiki.archlinux.org/index.php/Sy … r_stays_onThere's also https://wiki.archlinux.org/index.php/Al … o_ShutdownObviously you can use an alias e.g.alias halt='sudo sy
I'm having a fuss with it taking my clock correctly on machine.Now I know what I'm doing, I'm using ntpd.service on the other machines, so I don't have to fuss with the clock.Do a time sync with ntpdate <time.server.ip.address> to get the UTC to read the right time and then when you type date it should be your localtime.
karol wrote:Arch doesn't provide debug information in the packages, you need to compile them yourself https://wiki.archlinux.org/index.php/De … l_settingsSee also e.g. https://mailman.archlinux.org/pipermail … 17012.htmlThe answer to this mail:https://mailman.archlinux.org/pipermail … 17024.htmlis promising.