Roger Oberholtzer said the following on 07/19/2011 08:00 AM:
The ntp protocol would be most sane if it were transmitted only as UTC.
That is in fact the case as both Per and I have pointed out by reference.
What a local system decides to do with that information is a whole different question - and one the ntp protocol really can't address.
Sort of. NTP only has to set the itnernal - software I beelive - system clock. That runs on UTC.
openSUSE seems to expect that the system clock is UTC,
I think that is so. It has always been the case, to the best of my knowledge, with UNIX systems. It needs to be so since different users or different applciations may be working in different timezones, so each have their offset from UTC.
no matter what the battery clock is. Or this is how it looks to me.
I have referred to "man hwclock" and that seems to be the point at which the battery clock being UTC or local comes into it. Once again: <quote> -u, --utc --localtime Indicates that the Hardware Clock is kept in Coordinated Universal Time or local time, respectively. It is your choice whether to keep your clock in UTC or local time, but nothing in the clock tells which you've chosen. So this option is how you give that information to hwclock. If you specify the wrong one of these options (or specify neither and take a wrong default), both setting and querying of the Hardware Clock will be messed up. If you specify neither --utc nor --localtime , the default is whichever was specified the last time hwclock was used to set the clock (i.e. hwclock was successfully run with the --set, --systohc, or --adjust options), as recorded in the adjtime file. <quote> -- "Nothing is more difficult to carry out, nor more doubtful of success, nor more dangerous to handle, than to initiate a new order of things." -- Machiavelli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org