On 2012-01-06, Rob van der Putten <[email protected]> wrote: > Hi there > > > unruh wrote: > >> Not sure what you are saying. "it does"-- what does? And what does >> 'right' mean here. > > 'right' is just a directory name. 'it does' means the file contains leap > second info; > > file /usr/share/zoneinfo/posix/Europe/Amsterdam > /usr/share/zoneinfo/posix/Europe/Amsterdam: timezone data, version 2, 13 > gmt time flags, 13 std time flags, no leap seconds, 180 transition > times, 13 abbreviation chars > > file /usr/share/zoneinfo/right/Europe/Amsterdam > /usr/share/zoneinfo/right/Europe/Amsterdam: timezone data, version 2, 13 > gmt time flags, 13 std time flags, 24 leap seconds, 180 transition > times, 13 abbreviation chars > > I have no idea how to extract leap second info from this file. > > Does ntpd actually use files from the /usr/share/zoneinfo/right/ tree? > I'm used to files like leap-seconds.3427142400.
No. That file tells yo uhow to make the translation from the time on your system to the time which will get you to the trains on time. This says that someone decided (as with all fanatics) that not having leapseconds on their system time is the "right" way to do things, and thus to translate from that to the time needed to get the train on time requires not only a time zone information but also leapseconds information. It has nothing to do with ntp. ntp only synchronizes the time on your machine with that on a server. If your server ( as most do) used UTC, your system will use UTC. If the server uses TAI your machine will use TAI. NTP's only concession is that when a leapsecond occurs it has the software to make sure that that leapsecond transition takes place over as little time as possible (one second ideally). Everything else is up to the translation software ( useing the zoneinfo files) to translate from your system time to "civil" time. > >> If you want to run the French Revolutionary time, 100sec/min, 100min/hr, >> 10 hr/day, etc, go ahead. > > Months in alphabetical order would be nice. > >> That you will be out of step with everyone >> else is your problem. All I am saying is the "announcement" that a leap >> second will occur 6 months from now gives you and everyone else lots of >> time to plan for it. And the txdata2012a will contain the information >> necessary for making those plans, whatever they are. >> >> ntpd is a way of synchronizing your clock with everyone else's. That is >> all. What you do with that information is up to you. If you want your >> machine to add 35 sec to the time it reads from the computer clock, use >> the leapseconds file to do that, just as you now use the zoneinfo file >> to translate your machine's UTC to the time you actually live by, >> including daylight savings. If you want your machine time to be on TAI, >> you will have to find some ntp server somewhere that is also on TAI to >> synchronize to. That that might be hard is just the price you pay for >> being out of step with everyone else. It is only someone who is crazy >> who says that when they are out of step with everyone else, it is >> everyone else that should change to get into step with them. > > It would have to be implemented in a way that makes sense. A new > standard perhaps. Is anyone into this sort of thing? > > > Regards, > Rob _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
