augment ~bklog~ to handle this method of being called since it was
written with the intention of handling continuous streams of stdout.
+** TODO Create automatic setup scripts for logging
+Date Created: 2021-01-25T00:21Z
+
+Create bash scripts that automatically set up a ~ninfacyzga-1~ device
+to automatically run executables in ~exec/~ according to procedures
+described in ~doc/~.
+
+*** TODO Create setup script for location logging
+Date Created: 2021-01-25T00:24Z
+
+Setting up location logging script using ~bklog~ via ~cron~ job.
+
+*** TODO Create setup script for time tracking
+Date Created: 2021-01-25T00:25Z
+
+Setting up time tracking via ~chrony~.
+
* Finished Tasks
+** DONE Remove unused executables
+ CLOSED: [2021-01-25 Mon 00:07]
+Date Created: 2021-01-25T00:03Z
+
+Some unused executables are present in the ~exec/~ directory that are
+not used. An example is ~bkgpslog~ which has been superceded by
+~gpspipe | bklog~.
+
** DONE ~/doc/time~: Migrate from ~ntpsec~ to ~chrony~
CLOSED: [2020-10-19 Mon 03:48]
The ~ntpsec~ package is in the ~dfsg~ Debian repository instead of the
~gpsd~ documentation for communicating to ~chrony~ via
~/run/chrony.XXXX.sock~ and ~/run/chrony.YYYY.sock~ sockets (for GPS
and PPS data respectively) can be found [[https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html#_feeding_chrony_from_gpsd][here]].
+
*** Closing comments (bktei):
~chrony~ seems much simpler to configure. Its method for interfacing
with ~gpsd~ seems simpler as well. The fact that it displays time