Hi Paul, Just to saying that I saw this behaviour. More details below.
On Sun, Oct 02, 2016 at 06:15:42PM +0200, Paul de Weerd wrote: > > Since upgrading several machines to a more current snapshot (in an > effort to keep up to date with LibreSSL fixes), I noticed ntpd started > failing. Here's what I see on my laptop: > > Oct 2 17:50:15 drop doas: weerd ran command rcctl start ntpd as root from > /home/weerd > Oct 2 17:50:28 drop ntpd[17059]: Terminating > Oct 2 17:52:50 drop doas: weerd ran command rcctl start ntpd as root from > /home/weerd > Oct 2 17:53:03 drop ntpd[27986]: Terminating > Oct 2 17:53:18 drop doas: weerd ran command ktrace -d ntpd -v as root from > /home/weerd > Oct 2 17:53:30 drop ntpd[97855]: Terminating > > I have ntpd_flags="-v" in my /etc/rc.conf.local, but the above is all > the logging output I get (that's from my *.* syslog file, that also > includes DEBUG output). for me, no override of ntpd_flags. ntpd.conf configured as: servers fr.pool.ntp.org constraints from www.duckduckgo.com > So far, 5 machines have been upgraded and 4 of them show this behavior > (although my laptop is now really fast to exit). These are all amd64 > machines (because I haven't gotten around to upgrading the few i386 I > still have running yet). They're 'real' and virtual (KVM) machines. I saw it on two amd64 hosts. I have i386 hosts (but the config is differents: use local servers). > Has anyone else seen this behavior? yes. I also tried to run with kern.nosuidcoredump=3 but the terminating don't generated any coredump in /var/crash/ntpd. the process terminaison isn't automatic: my ntpd is now running fine since almost 1 day. -- Sebastien Marie