use .otrw for waypoints dump

This commit is contained in:
Jan-Piet Mens
2015-10-20 08:50:20 +02:00
parent 92e1a0d7c3
commit bbe09b35aa
2 changed files with 2 additions and 2 deletions

View File

@@ -306,7 +306,7 @@ As mentioned earlier, data is stored in files, and these files are relative to `
* `msg/` contains messages received by the Messaging system.
* `photos/` optional; contains the binary photos from a _card_.
* `rec/` the recorder data proper. One subdirectory per user, one subdirectory therein per device. Data files are named `YYYY-MM.rec` (e.g. `2015-08.rec` for the data accumulated during the month of August 2015.
* `waypoints/` contains a directory per user and device. Therein are individual files named by a timestamp with the JSON payload of published (i.e. shared) waypoints. The file names are timestamps because the `tst` of a waypoint is its key. If a user publishes all waypoints from a device (Publish Waypoints), the payload is stored in this directory as `dump.json`.
* `waypoints/` contains a directory per user and device. Therein are individual files named by a timestamp with the JSON payload of published (i.e. shared) waypoints. The file names are timestamps because the `tst` of a waypoint is its key. If a user publishes all waypoints from a device (Publish Waypoints), the payload is stored in this directory as `username-device.otrw`. (Note, that this is the JSON waypoints import format.)
You should definitely **not** modify or touch these files: they remain under the control of the _recorder_. You can of course, remove old `.rec` files if they consume too much space.

View File

@@ -343,7 +343,7 @@ void waypoints_dump(struct udata *ud, UT_string *username, UT_string *device, ch
return;
}
utstring_printf(ts, "/dump.json");
utstring_printf(ts, "/%s-%s.otrw", UB(username), UB(device));
if (ud->verbose) {
printf("Received waypoints dump, storing at %s\n", UB(ts));
}