Hi Schelte,
Good to hear it works for you --so something must be different on my side.
I did some more experiments:
- I realized: the behavior for gui and daemon mode is the same:
- after entering interval, data fields, and filename for the first time using the gui, all works as expected
- if restarting in gui- or the daemon-mode, the datalog does not work - The user for daemon mode and gui mode is the same.
- Checking the configuration via the web server shows the check mark for the datalog and the append mode (see attachment)
- If I use this command line
- Code: Select all
/usr/local/bin/otmonitor --daemon --datafile=/home/pi/otdata.txt --append
the datalog works as expected.
So, it seems, the settings in .config/otmonitor/otmonitor.conf file are somehow ignored in my system (raspberry-3, debian jessie, otmonitor with the 'dash-patch' I've sent a few weeks back).
I can live with this solution, but it's strange that the system does not behave as it should.
I had a quick look into otmonitor.tcl
I found where the command line options are parsed and eventually the command line options overwrite the settings from the config file
- Code: Select all
# Now override with the collected command line options
foreach n [array names optcfg] {
set cfg($n) $optcfg($n)
}
I could not find the parsing of the config file itself --any hints?
Best,
Thomas