TLG Front end clock drift problems
Denise told me that Rich did "something" on Dec. 24, but today the problem is persisting.
I note that TLG has
- ld (1, 1, "vxworks_boot/v6.4/module/mv5500/sntpctod-latest.out");
- todUpdateTime ("fecode-bd")
- period 300, todUpdateTime,0
If you need to cancel that because it conflicts with Rich's method or whatever, it is just the task named "t1".
Also, I saw that TLG's startup script is "commented out" from auto-running, in that it is named as .login_tlgx in the boot params, but the real file is named .login_tlg. Is this intentional?
#1 Updated by Richard Neswold about 1 year ago
- Status changed from New to Feedback
I ran (12:26, 12:30pm) this command, a standard way of requesting periodic clock resets
period 300, todUpdateTime, 0
We were going to do this very thing.
TLGTST is running this periodic task and, when Linden gave the go-ahead, I was going to enable it on
Now Linden can see if the operational node is affected by periodic time updates. It should be noted that both Linden and I didn't think the system should be sensitive to these updates, but we were being conservative.
It should also be noted that this is a band-aid to the real problem which resides in the IP-UCD driver. This "fix" runs every 5 minutes so the time could be off for up to 5 minutes before getting corrected.
Also, I saw that
TLG's startup script is "commented out" from auto-running, in that it is named as
.login_tlgxin the boot params, but the real file is named
.login_tlg. Is this intentional?
Yes. Charlie did this for some reason. Linden, could you append the reason so it's documented?