That newpeer stuff is just the tip of an iceberg. There should be a lot more
when the DNS code actually does a lookup and processes an answer.
My plan is to remove most of it. It's high on my list, but I need some quiet
time and/or I got distracted by the recent seccomp cleanup.
Feel free to
Hey Hal,
Is this DNS debugging intended for syslog when I build without "--enable-debug"?
$ ./waf configure
$ sudo ./build/main/ntpd/ntpd -g -p /run/ntpd.pid
$
syslog shows:
2017-05-19T05:28:57.546+00:00 host.example.com ntpd[19012]: ntpd
ntpsec-0.9.7+616 2017-05-15T08:59:02-0400: Starting
2017
That sounds useful and productive. Unless GEM, ESR, or Hal have any
objection, feel free to go through the other existing tests and clean them
up the same way.
Thanks!
..m
On Wed, May 17, 2017 at 6:34 PM Ian Bruene via devel
wrote:
> Currently the tests follow a general format of a comment
Thanks.
Is there anything like strace that will collect all the info and write out a
summary rather than writing out a line for each syscall?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/m
