log timestamping - inconsistent timezones about beagle_sdr_gps HOT 5 OPEN

On Tue, Mar 23, 2021 at 2:30 PM John Seamons ***@***.***> wrote: This is incorrect. The Kiwi code does *not* change the Linux/Debian timezone. It should always be UTC. As the Beagle does not have an RTC (real-time clock) driver currently I don't know what set-local-rtc does. The Kiwi code does attempt to determine the timezone so it can show local time in the user interface in addition to UTC. It can only do this if it can determine the lat/lon. There are three ways of doing that: via GPS if it has a signal, from public ip address geo-location or, as a last resort, if the admin has entered a lat/lon on the admin page. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#498 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRUYNKB7P66VPPJT7XC3XTTFDM5HANCNFSM4ZVOB7CA> .

okay, then. but i did describe the issue with the timestamps in the Log tab of the Admin interface. having made the change specified, the log entry timestamps do not slew 4 hours ahead after the GPS is reacquired. i made no change to the timezone of any account. only set a flag to notify how to interpret output from hwclock. On Tue, Mar 23, 2021 at 2:30 PM John Seamons ***@***.***> wrote: > This is incorrect. The Kiwi code does *not* change the Linux/Debian > timezone. It should always be UTC. As the Beagle does not have an RTC > (real-time clock) driver currently I don't know what set-local-rtc does. > > The Kiwi code does attempt to determine the timezone so it can show local > time in the user interface in addition to UTC. It can only do this if it > can determine the lat/lon. There are three ways of doing that: via GPS if > it has a signal, from public ip address geo-location or, as a last resort, > if the admin has entered a lat/lon on the admin page. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#498 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABRUYNKB7P66VPPJT7XC3XTTFDM5HANCNFSM4ZVOB7CA> > . >

timezone for UI is still: > > TIMEZONE: "EDT", "America\/New_York" > > On Tue, Mar 23, 2021 at 7:29 PM Christopher Sylvain < ***@***.***> wrote: > okay, then. but i did describe the issue with the timestamps in the Log > tab of the Admin interface. having made the change specified, the log > entry timestamps do not slew 4 hours ahead after the GPS is reacquired. i > made no change to the timezone of any account. only set a flag to notify > how to interpret output from hwclock. > > > > On Tue, Mar 23, 2021 at 2:30 PM John Seamons ***@***.***> > wrote: > >> This is incorrect. The Kiwi code does *not* change the Linux/Debian >> timezone. It should always be UTC. As the Beagle does not have an RTC >> (real-time clock) driver currently I don't know what set-local-rtc does. >> >> The Kiwi code does attempt to determine the timezone so it can show >> local time in the user interface in addition to UTC. It can only do this if >> it can determine the lat/lon. There are three ways of doing that: via GPS >> if it has a signal, from public ip address geo-location or, as a last >> resort, if the admin has entered a lat/lon on the admin page. >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> <#498 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/ABRUYNKB7P66VPPJT7XC3XTTFDM5HANCNFSM4ZVOB7CA> >> . >> >