Re: hwclock problem with leapseconds - posix?

cc-tec@xxxxxx writes:

hi group,

thks to all,

@all:
- pls. do not! contribute to this thread if you think a reliable time
basis and source is something neglectable,
- pls. do not! contribute to this thread if you think djb's ideas of
relying on tai is wrong,
- pls. do not! contribute to this thread if you think the systematic
fault of hwclock of misssetting the rtc can be corrected by --adjust,
- pls. do not! contribute to this thread if you think 23 seconds (or
22) are nothing to worry about,
- pls. do not! contribute to this thread if you mainly like to explain
how well you and your notebook work together,
- pls do not! contribute to this thread if you think i should fix
hwclock myself, i'm near an attempt to try, but have very little time
and very few skills in this direction, and explained this already,

You might have noticed that this would have given you no answers
whatsoever. That is of course fine.


all others, especially persons who have read djb's site and do work on
the same point / problem are sincerely invited to add to this
analysis,

@Old guy
NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.

i'll try on the next problem, for the moment it's a decision between
keeping this thread and starting a new one,

What has that got to do with posting from googlegroups. I use nn on my own
system, and reply to this group.


What distribution?

i'd write it, sles (SuSE Linux Enterprise Server) incl. the accurate
version, above, pls. check there, it (sles) does! set the system time
from rtc on bootup, and does! write it back on shutdown, but does do
the second in a wrong way with 22 or 23 seconds fault when configured
to use 'tai' and the 'right' zoneinfo file,

boot time, network, timestamps,

as a fundumentalist - hi cia - i'd like to have correct times even if
network connection is broken, plausible?

The question os which right time. Most people call UTC ( with timezone
adjustments) the "right" time.


22, 23 or 33 seconds,

the current utc - tai leap is 33 secs, 10 of them are already included
in the unix epoch (??? or something similar) so that on wrong gameplay
between different parts of a system 23 show up as gap, 22 on systems
who use old (from before 2005-01-01) leapsecs.dat files,

You are worried and use an old leapsecond file?



hwclock with
those two options does not introduce a _difference_ in the times

Here, the RTC in trashbox7 is set to localtime (DST isn't used here).

thats plausible for me, i think 'my' differences come from the
calculations the system has do to between utc and localtime, your's
does not have to do those, localtime - afaik - is ok for people
without dst, others need utc to get automated switch to and from dst,

What time is your rtc clock? I thought it WAS UTC. Is it actually
localtime.
Note that system time knowns nothing about local time.



What timezone are you using in the system

Europe/Berlin, but from the 'right' subdir, as explained above,

(what does the shell variable TZ return,

how to check?

or what does /etc/localtime point to,

at the moment: /usr/share/zoneinfo/Europe/Berlin, as i do it the
'dirty' way, the problems occur when it's pointed to /usr/share/
zoneinfo/right/Europe/Berlin

Do not "point it" Copy the right file into /etc/localtime. That link may
not be up when the system boots and sets the system clock, and if it needs
info from /usr/share/zoneinfo, that info might not be there.



or if all else fails, what does '/bin/date ; /bin/date -u' show)?

with the normal (wrong) zonefiles: cet and utc one hour apart, seconds
exact, what shall be normal for german winter,

Why not post it.
And also what does
hwclock
show.



with /usr/share/zoneinfo/right/Europe/Berlin nearly the same, but the
utc time being 23 seconds less than one hour behind cet, what's a
little confusing - isn't it?
concrete:
Fri Jan 4 19:48:00 CET 2008
Fri Jan 4 18:48:23 UTC 2008

@Unruh:

He has gotten convinced by djb that everyone else in the world does things
wrongly

not everyone, but most people??

and badly,

just a little,

and wants to have his system on Bernstein time,

'Bernstein Time' is tai, invented some decades back as solution for

No it is not. As has been pointed out, TAI is 33 sec, not 23 sec off from
UTC.


the urgent need of a stable monotone time base, try gps without or
trash satellites with other sources, your problem,

rather than UTC with the zoneinfo files translating from Bernstein time to UTC.

it's not! only the need for exact time, it's also some

UTC IS exact time. It is not tai, but so what? It is just as exact as TAI
or Bernstein time. It is just different.
And the world uses UTC for timekeeping.

fundamentalistic mentality to want things to be solved in a clear and
accurate way, and to help others not to waste time in investigations
on the same problem again,

i hope this will be read by someone who can help,

We are trying. The fact that you have set ideas as to what constitutes help
does not help.

Is your rtc on localtime or on "UTC" . Look in your operating system files
to see which you tell it your rtc is on. If it is on utc, then as has been
pointed out hwclock does not behave as you claim it does. If it is on
localtime, then it may be that on bootup the leapseconds file or the
zoneinfo file are not available.


However, your requests are still weird. You demand that people give you
exactly the help you think you need, but do not want to pay anyone. If you
pay me $500/hr, plus airfare, I will come over and look into why your
system is misbehaving.




helpless user,

.

Relevant Pages

  • Re: hwclock problem with leapseconds - posix?
    ... preferably i also want the rtc updated during normal running system, ... You are using modified TAI, ... I have no idea what a leapsecond respecting timezone is. ... served better by using UTC. ...
    (comp.os.linux.setup)
  • Re: hwclock problem with leapseconds - posix?
    ... a quick look shows that hwclock uses the routines mktime with the timezone ... I suspect that the assumption that we are using UTC, not TAI, and that the ... preferably i also want the rtc updated during normal running system, ...
    (comp.os.linux.setup)
  • Re: hwclock problem with leapseconds - posix?
    ... preferably i also want the rtc updated during normal running system, ... utilities, the timezone files ore wherever, i cannot, can please ... served better by using UTC. ... as far as i understand i do not set the system to tai, ...
    (comp.os.linux.setup)
  • Solaris RTC
    ... I was checking to verify that Solaris uses UTC ... use localtime but UTC time like the rest of the world. ... Except apparently, Solaris x86. ... have a choice for the RTC, ...
    (comp.unix.solaris)
  • Re: after reboot computer time is changed
    ... updates the RTC with that wrong time later, ... assumes that the rtc time is UTC on bootup. ... localtime. ... Thus the clock will ...
    (comp.os.linux.setup)