**** BEGIN LOGGING AT Sat May 12 02:59:59 2012
May 12 16:57:24 <slapin> hi, all!
May 12 16:57:35 <slapin> have anybody used ntpd+gpsd lately?
May 12 17:04:12 <Marex> slapin: IIRC HPA complained about GPSd
May 12 17:04:15 <Marex> why ?
May 12 17:04:42 <slapin> who complained?
May 12 17:04:51 <slapin> gpsd works perfectly here
May 12 17:05:02 <slapin> that's ntpd problem, actually
May 12 17:05:09 <slapin> or something
May 12 17:06:17 <slapin> guys at ntp.org don't trust year from refclocks and prefer to detect it and this requires constraining time difference to be within 4 hours
May 12 17:06:46 <slapin> and they don't want year from gpsd
May 12 17:07:26 <slapin> and they are still in 80s when time chips actually either didn't provided year or miscalculated it
May 12 17:08:47 <slapin> actually only thing I need is some script to poll if gps is locked, and as it locked, set time properly
May 12 17:09:12 <slapin> and restart ntpd
May 12 17:09:25 <slapin> and then I resolve major time issues here
May 12 17:11:05 <slapin> these people forgot to install batteries in thousands of devices, and they start in 1970, and can't set time over NTP because they don't have internet access, and only have luck having GPS which might be wrong, too if out of sky for some time.
May 12 17:13:04 <slapin> old sw did not use NTP, and set time evry 5 seconds from gps, which often lead to problems, ntpd will disallow this, but this first time time setting is really major pain in ass
May 12 17:13:34 <slapin> Marex: wtf is HPA?
May 12 17:34:39 <Marex> H Peter Anvin ?
May 12 18:26:45 <slapin> Marex: and what he had against gpsd?
May 12 18:38:07 <Marex> that the gps detection algo is borked
May 12 18:38:09 <Marex> I think so too
May 12 18:38:11 <Marex> it is
**** ENDING LOGGING AT Sun May 13 02:59:59 2012