I am trying to use my volumio to wake up and thus checked the ntp was running properly to keep the clock accurate. I am using volumio 1.51 on Rpi.
ntp seems to be indeed started at boot time and generates a ntp.pid in /var/run. However when i log in after boot and check with ps, the process is gone.
When i re-start it manually from root account, it works nicely. Looks like some process is stopping it on purpose during teh boot sequence.
Is that intended? If that’s the case, wouldn’t it be better to control the ntp polling period to a long (7 days??) value and keep it running?
It’s a feature, not a bug. The ntpd service is automatically disabled by default in the orion_optimize.sh script along with a few other services, like cron. You can enable it by commenting out line 39 as such: