I'm at Asia/Omsk timezone that is GMT+7 now and I see following in syslog (using syslog-ng): Jun 14 06:42:45 storage ntpd[4540]: peer 192.108.114.23 now valid Jun 14 13:43:42 storage ntpd[4539]: adjusting local clock by 1.106534s Jun 14 06:47:07 storage ntpd[4540]: peer 130.226.232.145 now invalid That looks insane. I fixed the issue replacing /var/empty with /var/chroot and copying /etc/localtime to /var/chroot/etc/localtime, I had to fix both /etc/conf.d/ntpd and `ntp` user home directory. I suppose ebuild should generate "better" chroot for openntpd. I'm not sure if /var/chroot/etc/localtime should be updated once (in ebuild) or every time /etc/localtime changes (e.g. in /etc/init.d/ntpd script).
this is fixed in 3.9_p1-r2 - please test. sorry for the delay - thanks for the report. kind regards Thilo
Should not openntpd.rc-3.9_p1-r2 be #prepare chroot - mkdir -p /var/lib/openntpd/chroot/etc/ - cp /etc/localtime /var/lib/openntpd/chroot/etc + mkdir -p ${NTPD_HOME}/etc/ + cp /etc/localtime ${NTPD_HOME}/etc ?
yes - thanks. committed.