On Tue, Nov 10, 2020 at 2:15 PM Bruce Labitt
wrote:
> "Dumb" machine, while actually computer controlled, is closed source.
> No possibility of changing its behavior.
> No ssh, no network. It's a data logger to an SD card. I have to use
> sneaker net to transport data to my PC.
>
> Other
If some variation of that sleazy hack doesn't work and you can't
find some some source for the info you want (maybe something like
https://isDSTactiveInMyTimezone.com/ :) then you'll have to determine
if DST is active on your own.
That requires a timezone file for your locale and some source
"Dumb" machine, while actually computer controlled, is closed source.
No possibility of changing its behavior.
No ssh, no network. It's a data logger to an SD card. I have to use
sneaker net to transport data to my PC.
Other possibility (after a SD card backup) is to change the dumb machine
The basic Unix time was to set up an epoch based on UTC time. This way when
systems talk to each other they are on the same time basis. So, each
machine needs to know what offset from utc, and whether or not it is on std
or daylight time.
--
Jerry Feldman
Boston Linux and Unix http://www.blu.org
You can mess around with DST and such but this slightly sleazy hack
might serve an alternative: find some way to get your "dumb" machine to
tell your "smart" machine what time it thinks it is currently, and then
force the smart machine to that time. For example, if SSH works from
the smart
Still looking at a time related bug. Wondering how (nowadays) linux
handles TZ and DST/ST transition.
Does linux embed DST state into TZ? Or is there a variable with a name
like "DST"?
I want to set two different machines, one a PC, the other a dumb
instrument to the same time. The dumb
