midnight roll be a configurable offset

[fmadio]

As the localtime on the box is not always the real time at the devices location. Rolling at midnight local time might be during an active time at the devices physical location.

Allow some kind offset when computing when midnight rolls occour

[fmadio]

in /opt/fmadio/etc/time.lua

New table entry

Scheduler.TimeOffset = 60 * 60e9 (offsets in ns)

this in effect changes the start/stop time of the capture and analytics scheduler, so that it can cross midnight boundaries in local time.

in the above the offsets is an additional 1 hour. this the 00:00 start time is actually 01:00 in the local timezone.

[fmadio]

updated

https://github.com/fmadio/fmadio20/commit/d272d8bd1d2a380f16ee0e25262666e45e39ebac

Configuration via /opt/fmadio/etc/time.lua

Example offset JST to GMT

[fmadio]

released FW 6641

[fmadio]

didnt actually work.... its more complicated as each capture process does the midnight roll also. so disabling the capture process midnight roll and rely entirely on the scheduler to manage it.

it also assumes theres no 24/7 capture, which makes sense as if 24/7 capture is enabled then there is no point having a time offset

[fmadio]

100G capture process updated

20G capture process updated

long run test in progress

[fmadio]

released, closing