| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
between our LOG_ERR and the syslog() macro by changing ours to
LOG_ERROR.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch defines a uniform set of log levels and changes all gpsd_report()
instances to use them. In most cases (I'd say about 80%) this will make
no observable difference, as the numeric log levels the code was using were
not too badly inconsistent anyway. The new log level macros are defined
and described in gpsd.h.
The main thing I wanted was to be able to consistently force dumping
of all I/O to devices and clients with -D 4. Some drivers didn't honor
this. One or two still may not through lack of an internal write() wrapper
that does logging; there will need to be some followup changes.
Level 0 messages are always displayed, but to make the semantics clearer
there are two defines LOG_ERR and LOG_SHOUT.
Level 5 is still super-raw I/O reporting. Level 6 and 7 messages are
tagged RAW_LOG+1 and RAW_LOG+2; I was particularly careful about these
because we have one report of a user who is getting good results from
Garmin serial only at -D 7 or up, and perish forbid I should interfere
with that bug being found.
|
|
|
|
|
|
| |
...for those who want to build their own apps linked against libgps and
want the headers to work. Works on OpenBSD, tested by Jeff Francis on
OS X and Linux
|
|
|
|
| |
First line where possible, second line for scripts called with #!
|
|
|
|
| |
Test the return value appropriately.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
...within the distance threshold and connect to the closest one that
is actually up.
|
| |
|
| |
|
| |
|
|
The DGPSIP socket is now part of the session context; it's guarded by
the same select as all other socket reads. The latest RTCM104 report
from it is relayed to each attached GPS when appropriate. (The old
code only passed a correction to the first GPS to be polled after the
report came in from the server.)
|