in relayd we use -v for that, so you need to run -dvvvv 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 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 verbose debug messages.
>
> Index: ntpd.8
> ===================================================================
> RCS file: /cvs/src/usr.sbin/ntpd/ntpd.8,v
> retrieving revision 1.40
> diff -u -p -u -p -r1.40 ntpd.8
> --- ntpd.8 30 Oct 2015 16:41:53 -0000 1.40
> +++ ntpd.8 20 Jan 2016 12:31:16 -0000
> @@ -50,6 +50,7 @@ If this option is specified,
> .Nm
> will run in the foreground and log to
> .Em stderr .
> +It may be specified again to enable more verbose debug logs.
> .It Fl f Ar file
> Use
> .Ar file
> Index: ntpd.c
> ===================================================================
> RCS file: /cvs/src/usr.sbin/ntpd/ntpd.c,v
> retrieving revision 1.103
> diff -u -p -u -p -r1.103 ntpd.c
> --- ntpd.c 11 Jan 2016 15:30:56 -0000 1.103
> +++ ntpd.c 20 Jan 2016 12:31:16 -0000
> @@ -137,7 +137,7 @@ main(int argc, char *argv[])
> while ((ch = getopt(argc, argv, "df:nsSv")) != -1) {
> switch (ch) {
> case 'd':
> - lconf.debug = 1;
> + lconf.debug++;
> log_verbose(1);
> break;
> case 'f':
>
--
