I have the GPS daemon running as user gpsd:

/usr/sbin/gpsd -N /dev/ttyUSB0 /dev/ttyUSB0

I have gpxlogger running as root:

gpxlogger -d -f /data/%Y%m%d-%H%M%S.gpx

Initially, all what gpxlogger writes is the gpx preamble, but no actual fixes.

gpxlogger starts to log actual fixes, as soon as I run another gpsd client like 'cgps -d' or 'gpsmon'. When this other gpsd client ends, gpxlogger stops to log fixes after some time.

It appears as if gpxlogger is not a "sufficient" client "to make" gpsd provide actual fixes.

For now my workaround is to autostart "cgps -s" in a terminal.

  • For now my workaround is to autostart "cgps -s" in a terminal. – Max Spring Apr 21 '19 at 19:37

Another closer look into the gpxlogger's manpage revealed to use the -e <export-method> with -l listing all available export methods. So now I invoke gpxlogger this way and it gets the fixes without another gpsd client running:

gpxlogger -e sockets -d -f /data/%Y%m%d-%H%M%S.gpx
  • 1
    As you've found your own answer you can accept your own answer as the answer. – Roger Jones Jun 12 '19 at 9:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.