Re: ntpd: really enable debug messages

2016-01-24 Thread Brent Cook
On Sat, Jan 23, 2016 at 08:48:22PM +0100, Reyk Floeter wrote: > On Sat, Jan 23, 2016 at 12:39:19PM -0600, Brent Cook wrote: > > I'm going with this instead. That way it works like the manual > > specifies already (-v enables logging debug messages) > > > > Yes, the -v flag is better, but see below.

Re: ntpd: really enable debug messages

2016-01-23 Thread Reyk Floeter
On Sat, Jan 23, 2016 at 12:39:19PM -0600, Brent Cook wrote: > I'm going with this instead. That way it works like the manual > specifies already (-v enables logging debug messages) > Yes, the -v flag is better, but see below. > cvs server: Diffing . > Index: ntpd.c >

Re: ntpd: really enable debug messages

2016-01-23 Thread Brent Cook
I'm going with this instead. That way it works like the manual specifies already (-v enables logging debug messages) cvs server: Diffing . Index: ntpd.c === RCS file: /cvs/src/usr.sbin/ntpd/ntpd.c,v retrieving revision 1.103 diff -u -

Re: ntpd: really enable debug messages

2016-01-20 Thread Sebastian Benoit
in relayd we use -v for that, so you need to run -d to get lots of output. check main() there? i think thats more intuitive, but maybe i'm just used to it. Brent Cook(bust...@gmail.com) on 2016.01.20 06:31:44 -0600: > Since the relatively recent logging unification, log_init needs a > debug l

ntpd: really enable debug messages

2016-01-20 Thread Brent Cook
Since the relatively recent logging unification, log_init needs a debug level > 1 in order for log_debug to print anything. This change makes it so 'ntpd -d' stays in the foreground but doesn't log much (the current behavior, different than previous releases though), 'ntpd -dd' actually prints more