[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Updated docs on NTP segment management
From: |
Hal Murray |
Subject: |
Re: [gpsd-dev] Updated docs on NTP segment management |
Date: |
Tue, 03 Mar 2015 13:57:44 -0800 |
address@hidden said:
> Pearly had a question about sending pps=on to an old gpsd. I assume if an
> older gpsd gets an unknown option it ignores it? Would be good to know
> going forward that is a policy.
Ignoring things complicates debugging.
address@hidden said:
> The JSON parser throws an error on unknown attributes, but attribute
> settings before the point of error are not invalidated. Put pps=on last.
Does it stop parsing/processing? Something like "pps=on" is well defined.
I'd vote for returning some sort of error message and documenting what
happens both before and after the error.
What does gpsd do with malformed input?
--
These are my opinions. I hate spam.
- Re: [gpsd-dev] Updated docs on NTP segment management, (continued)
Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/03
Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Gary E. Miller, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Gary E. Miller, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Gary E. Miller, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Eric S. Raymond, 2015/03/07
- Re: [gpsd-dev] Updated docs on NTP segment management, Harlan Stenn, 2015/03/07