DOC 6501_Release V
ATS-6501 Users Guide
195
2840140800 25 #Mon Jan 1 00:00:00 1990
2871676800 26 #Tue Jan 1 00:00:00 1991
2918937600 27 #Wed Jul 1 00:00:00 1992
2950473600 28 #Thu Jul 1 00:00:00 1993
2982009600 29 #Fri Jul 1 00:00:00 1994
3029443200 30 #Mon Jan 1 00:00:00 1996
3076704000 31 #Tue Jul 1 00:00:00 1997
3124137600 32 #Fri Jan 1 00:00:00 1999
3345062400 33 #Sun Jan 1 00:00:00 2006
3439756800 34 #Thu Jan 1 00:00:00 2009
3550089600 35 #Sun Jul 1 00:00:00 2012
ATS-6501>
c. Verify the expiration date and update date for this file are later and the date/time set
using the manual recovery method. Also make sure the last line is the file contains the
correct leap second.
d. The epoch for this file is 1 Jan 1900. Each of these fields contains the number of
seconds since that epoch.
e. Use an editor (i.e. vi) to edit the file if needed (vi /mod/tsc/leap-seconds.list)
f. Copy the original file in case errors are made while editing. You can use this file as an
example just in case. cp /mod/tsc/leap-seconds.list /mod/tsc/leap-seconds.ori
g. If necessary, adjust the expiration date to 30 Jun or 31 Dec 23:59:59 (whichever is
sooner) and get the correct number of seconds for that date/time and enter that value
after the @ sign. Make sure to follow the format in the file.
h. Use the current date/time to update the Update field.
i. If necessary add a line to the bottom of the file to add the new leapsecond following the
same format.
j. Save the changes to the file and exit the editor.
k. The system should pick up the new settings immediately.
Note: Under normal operations when the GNSS reference is present the system will get the
current leap-second information and update this file automatically.
To Next Page
