Re: LOGIF

2020-04-15 Thread Hal Murray via devel
Gary said: > Then hang it off another switch. Care to suggest "another switch"? > but it does burn out SD cards quickly. >From my initial message: They are all very low volume I was close to saying they all happened only during initialization, but at least one is termination, and I

Re: LOGIF

2020-04-15 Thread Gary E. Miller via devel
Yo Hal! On Wed, 15 Apr 2020 19:49:18 -0700 Hal Murray via devel wrote: > Gary said: > > Sorry, I misread that. Some people want verbose logging, some > > none. Choice is good. As long as there is an on/off switch of some > > sort. > > Yes and no. > > The on/off switch is obscure enough

Re: LOGIF

2020-04-15 Thread Hal Murray via devel
Gary said: > Sorry, I misread that. Some people want verbose logging, some none. Choice > is good. As long as there is an on/off switch of some sort. Yes and no. The on/off switch is obscure enough and the amount of logging that can be turned on/off is small enough that the choice isn't

Re: LOGIF

2020-04-15 Thread Gary E. Miller via devel
Yo Hal! On Wed, 15 Apr 2020 18:49:18 -0700 Hal Murray via devel wrote: > Gary said: > >> They are all very low volume that are useful for debugging, > >> especially when somebody asks for help on users@ or devel@ > > > Why remove something you think is useful? > > Ahh/oops. > > I didn't

Re: LOGIF

2020-04-15 Thread Hal Murray via devel
Gary said: >> They are all very low volume that are useful for debugging, >> especially when somebody asks for help on users@ or devel@ > Why remove something you think is useful? Ahh/oops. I didn't want to remove the messages, just remove the LOGIF wrapper so the messages would always

Re: LOGIF

2020-04-15 Thread Gary E. Miller via devel
Yo Hal! On Wed, 15 Apr 2020 18:37:50 -0700 Hal Murray via devel wrote: > Anybody object if I remove it? Well, you also said: > They are all very low volume that are useful for debugging, > especially when somebody asks for help on users@ or devel@ Why remove something you think is useful?

LOGIF

2020-04-15 Thread Hal Murray via devel
Anybody object if I remove it? It's used to conditionalize logging of various messages from refclocks. You will see them if your ntp.conf has" logconfig +clockall (and won't see them by default) include/ntp_syslog.h:#define LOGIF(nlog_suffix, msl_args) \

Re: 1.1.6 build fails on FC30

2020-04-15 Thread Hal Murray via devel
> So no error messages about gps/NMEA. > NMEA(0) .GPS.0 l 15 64 377 > 0. 0. 0.0019 What's the line for that in your ntp.conf? Any fudge lines? What does stty say for the baud rate? What sort of GPS device ? What baud rate is it

Re: 1.1.6 build fails on FC30

2020-04-15 Thread Udo van den Heuvel via devel
On 12-04-2020 17:35, Udo van den Heuvel via devel wrote: > On 12-04-2020 17:25, ASSI via devel wrote: >>> # ppswatch /chroot/ntpd/dev/pps0 >>> (shows similar output) >> >> Good, but does ntpd see the same? > > Well, devices look like this: And pps debug messages: # dmesg|grep event [