Re: [ntp:questions] Can i control the NTP Sync?

2008-08-13 Thread David J Taylor
Unruh wrote:
[]
 ntp knows nothing about time zones. It gets the remote time in UTC.
 time zone info is all handled by your local machine. On unix/linux/..
 (sensible machnes) the machine time is ALWAYS UTC. time routines do
 the translation using a file called /etc/localtime. On windows it is
 more difficult, since Microsoft has never heard of timezones, so you
 have to kludge it yourself. Exactly how your machine or your
 implimentation of ntp kludges it I do not know.

No, you do not need to kludge it yourself with Windows - there is a set 
of routines built into Windows you can call if you wish to get local time, 
and a set of registry values provided and updated with Windows which allow 
it to keep local time in just the same way as other systems.  If you have 
to intervene manually you are doing something wrong.  Windows, like many 
modern OSes, works in UTC internally.

David 


___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions


Re: [ntp:questions] Can i control the NTP Sync?

2008-08-13 Thread David Woolley
Unruh wrote:

 machnes) the machine time is ALWAYS UTC. time routines do the translation
 using a file called /etc/localtime. On windows it is more difficult, since

Not all Unixes use the Olson package and some may use a different 
location for this file.  Some Unixes, in current use, encode the rules 
in an environment variable, which needs to be changed when the rules 
change (but not when the clocks change), and thus an application 
restart. Earlier ones only allowed the base timezone offset to be 
changed but had the, historic, US timezone rules hardcoded.  I think the 
original Unix did timezones only the kernel.

You will have some problems in exchanging media between Unix systems if 
you don't run them on UTC, as file timestamps are stored in the POSIX 
encoding of UTC and converted to local time by the ls command, etc.

 Microsoft has never heard of timezones, so you have to kludge it yourself. 

Microsoft have supported timezones since Windows 9x or earlier and have 
reasonably proper support since Windows NT.  For legacy reasons, they 
store wall clock time in the RTC hardware.  Windows encodes the rules in 
the registry and the registry needs updating when the rules change, but 
I don't think you need an application restart.  (Both the older Unix 
system and NT are limited to two changes and two offsets per year.)

 Exactly how your machine or your implimentation of ntp kludges it I do not
 know.

More precisely, you always need to specify what OS you are using.  Not 
specifying in an NTP context tends to imply Linux, but Linux tends to be 
leading edge and any recent one will use the Olson package.

___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions


Re: [ntp:questions] Can i control the NTP Sync?

2008-08-13 Thread David J Taylor
David Woolley wrote:
 David J Taylor wrote:

 it to keep local time in just the same way as other systems.  If you
 have to intervene manually you are doing something wrong.  Windows,
 like many modern OSes, works in UTC internally.

 Using UTC internally is, I think, only true of NT, and comes from its
 VMS heritage, rather than from its Windows one.

Well, since 1992!  NT 3.1, 3.5, 4, Windows 2000, XP , Vista etc!

I'm not talking 16-bit Windows or DOS.

  I seem to remember
 that Windows 3.x was not timezone aware, and I think that Windows 9.x
 only has per system timezone information and works internally on
  local time. (Quite a few home users still use Windows 95 and some
 small businesses probably still do so - it might also be in embedded
 systems used by larger businesses.)

32-bit Windows such as 95/98/ME etc. all support the same time API, and 
use UTC internally.

 FAT and VFAT filesystems always use local time.  I'm not sure about
 NTFS.

NTFS and CDFS (I think) use UTC.  Windows remains compatible when access 
the older file systes, as I hope would UNIX and its derivatives.

 Windows timezone handling is limited to a single pair of rules per
 timezone, with one (or zero) changes each way between two offsets. The 
 Olson package, used on most Linuxes and modern Unixes, can record
 all historic and all future changes, even if they are not reducible
 to one, simple, rule.

 Whilst you can force, at least some, NT systems to treat the RTC as
 UTC, most system administrators don't even know this.

It would be useful to have a record of leap seconds as well.  Is that in 
the Olson package?

For my own stuff - photos mainly - I stick with labelling in UTC time - no 
offsets at all.  My wife prefers local time in the country taken.  So her 
and my photos in Australia have names which are 11 hours (IIRC) different:

  2008-08-13-0100-1234.jpg
  2008-08-13-1200-1234.jpg

Can be fun when you are looking at photos from three different cameras 
taking multiple shots of the same subject (a group of friends on the 
Sydney Harbour bridge walk), all on (sigh) slightly different time 
settings (even though precisely synched before leaving home).

Cheers,
David 


___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions


Re: [ntp:questions] Can i control the NTP Sync?

2008-08-13 Thread Maarten Wiltink
David Woolley [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
[...]
 Using UTC internally is, I think, only true of NT, ...

Which, conveniently, is also the only Windows family that will run NTP.

Groetjes,
Maarten Wiltink


___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions


[ntp:questions] Can i control the NTP Sync?

2008-08-12 Thread Sami al flaish

Dear Experts,
I am thinking of using the NTP services, but I have one problem which is
When the time zone change from summer to winter or from winter to summer
So currently we have control on the local time and we changed manually when the 
time zone change, because we don’t change the local time on that machine even 
due the time zone changed if we have a running operation and we keep it this 
way until the ongoing job
Finish. So the problem here if we have the NTP server sync to that machine the 
sync will force the local time to change, which will affect our operation.
 
Any suggestion 
 
Regards,
Sami
_
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions