<div dir="auto">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. <br><br><div data-smartmail="gmail_signature">--<br>Jerry Feldman <<a href="mailto:gaf.linux@gmail.com">gaf.linux@gmail.com</a>><br>Boston Linux and Unix <a href="http://www.blu.org">http://www.blu.org</a><br>PGP key id: 6F6BB6E7<br>PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6<br>B B6E7</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 10, 2020, 1:24 PM Michael ODonnell <<a href="mailto:mod.gnhlug@b0rken.com">mod.gnhlug@b0rken.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
You can mess around with DST and such but this slightly sleazy hack<br>
might serve an alternative: find some way to get your "dumb" machine to<br>
tell your "smart" machine what time it thinks it is currently, and then<br>
force the smart machine to that time. For example, if SSH works from<br>
the smart machine to the dumb one then from the smart one you might say:<br>
<br>
% x="$(ssh dumb date)"<br>
% sudo date --set="$x"<br>
<br>
...or some variation on that theme.<br>
<br>
--M<br>
<br>
_______________________________________________<br>
gnhlug-discuss mailing list<br>
<a href="mailto:gnhlug-discuss@mail.gnhlug.org" target="_blank" rel="noreferrer">gnhlug-discuss@mail.gnhlug.org</a><br>
<a href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" rel="noreferrer noreferrer" target="_blank">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a><br>
</blockquote></div>