| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For simple logging of NMEA data or system performance analysis
it is often desirable to have high resolution time-stamps.
This implementation affects only the client-side, namely gpspipe.
Option -u was added to enable usec-resolution time output.
Furthermore, the default time format has been changed because
it is more desirable to have a standardized and sortable time-tag
default format instead of a locale-dependent one.
Also, the new option -u appends decimal digits to the seconds
which does not make sense for the some %c formats.
A future desirable feature might be to have usec resolution
timestamps on the gpsd protocol messages.
modified: gpspipe.c
modified: gpspipe.xml
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| | |
|
| |
|
|
| |
This was the easy part. Remaining removals will require more decisions.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This patch is backwards-compatible by adding a new option -T (note
capital case) for the timestamp format.
All tests pass.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The patch original is at:
https://lists.berlios.de/pipermail/gpsd-dev/attachments/20100111/85ad4e15/attachment.bin
This revision changes netlib_connectsock() to take a first argument that is
an address family and can specify IPv4, IPv6, or either. It also changes
gpsd.c to open two client sockets, one IPv4 and one IPv6, and listen
on both.
As a required cleanup, a number of defaults to "127.0.0.1" become
defaults to "localhost" so we're not hardwiring in IPv4 assumptions
anymore.
I've omitted a significant portion of the Mehani patch that changed the
interface of the client library in an incompatible way. Currently there is
no way to make gpsd listen to IPv4 or IPv6 only, and no way to make a
client query over IPV4 or IPv6 only. Also, we'd really like to be able to
condition out IPv6 or (someday) IPv4 support for a leaner runtime, and
there's no way to do that yet, either.
Under IPv4, regression tests pass; live operation with a GPS mouse and
the aishub feed both work. However, the resulting code does not splint
clean; this will need to be fixed, and that's going to be tricky due
to the new sockaddr_t struct.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
So it becomes wire-protocol-independent (no longer generating its own
?WATCH command). It still reads froom the session socket, rather than
doing gps_poll(), in order to avoide decode overhead.
Building on this, use the new WATCH_DEVICE flag to make gpspipe honor
the device part of a standard source specification, if that is
present.
Make -D an option for enabling client-library progress debugging.
Rename the -f (output-file) option to -o.
|
| | |
|
| | |
|
| |
|
|
| |
gpslogger.c itself to avoid duplication.
|
| |
|
|
|
|
| |
...to write output to a file (instead of stdout), and to sleep for ten
seconds before attempting to connect to gpsd (useful when running from
/etc/init.d/ as a daemon).
|
| |
|
|
|
| |
Would've been handy earlier today while I was running a few receivers
in parallel.
|
| |
|
|
|
| |
We may need to revisit this if 'n' when we get around to supporting
ipv6.
|
| | |
|
| |
|
|
|
|
| |
a spinner ("twirling baton") on stderr. this might be useful if you
are redirecting gpspipe output somewhere but want to see if gpspipe is
doing anything.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
Integrate gpspipe.
|
