s6-sntpclock: fatal: time uncertainty too large
you need to force the update, i think...
try this one, make a file in /etc/66/sysadmin/service/ntpclient
[main]
@ type=classic
@ name=ntpclient
@ description="ntpclient daemon"
@ user=(root)
@ options=(log env)
[start]
@ build=auto
@ execute=
(
if
{
pipeline
{
s6-setuidgid ntp
backtick -n NTPSERVERIP
{
pipeline { s6-dnsip4 -t 16000 pool.ntp.org }
s6-head -n 1
}
importas -u NTPSERVERIP NTPSERVERIP
execl-cmdline -s { s6-sntpclock ${CMD_ARGS} -v2 $NTPSERVERIP }
}
execl-cmdline -s { s6-clockadd ${CMD_ARGS} }
}
s6-setuidgid nobody
s6-sleep 14400
)
[environment]
!CMD_ARGS=-f
then 66-enable -f -S ntpclient
see what's happen. if all is good change the /etc/66/conf/ntpclient and replace the CMD_ARGS=-f by an empty one (meaning CMD_ARGS=), than 66-start -r ntpclient to reload the configuration file.
An option will come soon on 66-start to properly handle such a case when the configuration file is needed to be changed on the fly. Work like a charm on my machine but...