🚀 go-pugleaf

This is James again posting a second problem to the group pertaining to the
clock.

I posted in the previous message of three systems losing time and even gaining
time.  However I began to think about the times I have had problems with the
clock and it has always been in losing time and not gaining.

Here's my problem.  My two remote stations are identical with some few
exceptions.  They run the same programs and batch routines.  One specific
routine is using the "at" commands every 1/2 hours to check the contents of a
certain directory.  This "at" command failed due to a "too late" error at both
remote systems at approximately 1:16am to 1:44am (it could even be narrowed
down from 1:16am to 1:29am or so) on Sunday the 29th of April.  One "at" failed
at 1:30am and the other "at" failed at 1:45am.  There had been no problem with
either clock pertaining to gaining time until this day and both "at" commands
were running around the clock.

My questions are, did the system gain 1 hour because it thought it was daylight
savings time?

Does SysV bump up or take off an hour on the clock, depending on the season,
when it is time for daylight savings or do you manually change the clock as I
did this past savings time?

What else could have happened on this mysterious morning?

I know all these questions may have been answered weeks ago, but I was not a
user of new group until recently and apologize for repeat questions.

Thanks again,

JAMES