doc(setup):Note how to start syncthing automatically

[EVA-2020-02.git] / exec / bklog-plan.org

diff --git a/exec/bklog-plan.org b/exec/bklog-plan.org
index 597f653a5f8cc95fd5e2e16f462a60b65629fd99..9afaea9e3dcc44654876372656119a05b968bb98 100644 (file)
--- a/exec/bklog-plan.org
+++ b/exec/bklog-plan.org
@@ -1,5 +1,6 @@
 * bklog task list
 * bklog task list

-** TODO Adjust filename duration dynamically
+** DONE Adjust filename duration dynamically
+   CLOSED: [2020-07-14 Tue 22:17]

 2020-07-12T21:17Z; bktei> Currently, the "duration" component of the
 output filename for a given chunk is calculated from the ~bufferTTL~
 variable which does not necessarily reflect the amount of buffer lines
 2020-07-12T21:17Z; bktei> Currently, the "duration" component of the
 output filename for a given chunk is calculated from the ~bufferTTL~
 variable which does not necessarily reflect the amount of buffer lines


@@ -53,7 +54,11 @@ in seconds between ~bufferTimestampOld~ and ~bufferTimestampNew~ may
 be calculated and an appropriate duration string generated from the
 ~timeDuration()~ function.
 
 be calculated and an appropriate duration string generated from the
 ~timeDuration()~ function.
 

-** TODO Update ~SECONDS~ variable during while read loop
+2020-07-14T22:17:16Z; bktei> Initial adjustment of SECONDS
+implemented. Ongoing monitoring of end time of each buffer round
+~while read~ loop checked.
+** DONE Update ~SECONDS~ variable during while read loop
+   CLOSED: [2020-07-14 Tue 16:22]

 2020-07-14T00:58Z; bktei> The starting timestamps of each output file
 still drifts against system time. Although the ~while read~ loop does
 not lose data, the drift causes the output files to be named weirdly.
 2020-07-14T00:58Z; bktei> The starting timestamps of each output file
 still drifts against system time. Although the ~while read~ loop does
 not lose data, the drift causes the output files to be named weirdly.


@@ -67,11 +72,28 @@ number of lines being read in each buffer round should be tracked and
 a modulus comparison may be implemented within the ~while read~ loop
 so that a correction is made after some fraction of the expected lines
 to be read are read.
 a modulus comparison may be implemented within the ~while read~ loop
 so that a correction is made after some fraction of the expected lines
 to be read are read.

+
+2020-07-14T16:21Z; bktei> I ran a test to see if SECONDS drifts and it
+does not. The lag is caused by other synchronous commands. The
+solution will be to adjust the variables against which SECONDS is
+compared.

 ** TODO Account for "early-exit" bug in input script
 ** TODO Account for "early-exit" bug in input script

-2020-07-14T03:00Z; bktei> What happens if the script piping its stdout
-into ~bklog~ immediately exits without providing any stdout (ex: a
-python script with a missing module)? ~bklog~ should be able to detect
-the latest exit code and exit early. It should also be able to detect
-if the incoming pipe is closed.
+*** 2020-07-14T03:00Z; bktei>
+What happens if the script piping its stdout into ~bklog~ immediately
+exits without providing any stdout (ex: a python script with a missing
+module)? ~bklog~ should be able to detect the latest exit code and
+exit early. It should also be able to detect if the incoming pipe is
+closed.
+
+*** 2020-07-14T22:25Z; bktei> 
+Possible solution using ~dd~, ~od~, and ~if [ -z string ]~ [[https://unix.stackexchange.com/a/33055][here]].
+** TODO Support configuration file for storing options
+*** 2020-07-15T23:48Z;bktei>
+Support storing options in a ~$HOME/.config/bklog/options.conf~ file
+so individual calls to ~bklog~ don't have to be so long. Aliases can
+be used instead to make ~bklog~ calls shorter, but cron jobs don't
+necessarily source alias files. Explicitly reading options from a
+configuration file would be more reliable, although it complicates
+usage of ~bklog~.

 * bklog narrative
 
 * bklog narrative