Your message dated Sat, 08 Nov 2008 02:17:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#287060: fixed in chrony 1.23-4
has caused the Debian Bug report #287060,
regarding chrony: trimrtc takes 40 seconds to take effect
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
287060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287060
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: chrony
Version: 1.20-6
Severity: normal

trimrtc takes about 40 seconds to update the CMOS clock.  Is that
intentional, and if not, is there a way to speed it up?  One reason is
that I often suspend or shutdown or hibernate right after shutting
down a ppp or ethernet interface, before the trimrtc done by the
/etc/network/if-down.d script has had a chance to trim the rtc.

Related to that question, is it possible to update the rtc to more
accuracy than the usual 1 second resolution, just by waiting the
remaining fraction of a second and then adjusting the rtc?

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.4.27-200412041
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages chrony depends on:
ii  libc6                       2.3.2.ds1-18 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-4        Shared libraries for terminal hand
ii  libreadline4                4.3-11       GNU readline and history libraries

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 1.23-4

We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive:

chrony_1.23-4.diff.gz
  to pool/main/c/chrony/chrony_1.23-4.diff.gz
chrony_1.23-4.dsc
  to pool/main/c/chrony/chrony_1.23-4.dsc
chrony_1.23-4_amd64.deb
  to pool/main/c/chrony/chrony_1.23-4_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Hasler <[EMAIL PROTECTED]> (supplier of updated chrony package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 06 Nov 2008 10:38:58 -0600
Source: chrony
Binary: chrony
Architecture: source amd64
Version: 1.23-4
Distribution: unstable
Urgency: low
Maintainer: John Hasler <[EMAIL PROTECTED]>
Changed-By: John Hasler <[EMAIL PROTECTED]>
Description: 
 chrony     - Sets your computer's clock from time servers on the Net
Closes: 287060 348412 504000
Changes: 
 chrony (1.23-4) unstable; urgency=low
 .
   * Fixed dependency of init script on Pppconfig ip-up.d script by moving
     those lines into the init script.
 .
   * Added checks to try to make sure that Chronyd is really, really running.
     Changed Netstat call to use -n, added code to kill it if it hangs.
     Added code to kill Chronyc if it can't contact Chronyd.
     Discussed the HPET/rtc problem in NEWS.Debian.
 .
     Closes: #504000: init script hangs for a while might break upgrade
 .
   * Added missing initialization to create_instance() in ntp_core.c.
     This was why UTI_NormaliseTimeval() was being called with huge
     values at times.
 .
   * See comment on #195620 in 1.21z-6 below.  If you know of more LP64
     bugs reopen #348412 with a patch.
 .
     Closes: #348412: chronyc not LP64 compliant
 .
   * Added comment about sources being discarded to chrony.conf as suggested
     by Andreas Hübner in  #268289.
 .
   * This is normal behavior.
 .
     Closes: #287060: trimrtc takes 40 seconds to take effect
Checksums-Sha1: 
 80b7316e2e937b025c4e8af6c304d12a01bb53fb 1095 chrony_1.23-4.dsc
 3cd4d16dcc42f764e4e910257ed163f5d55b551f 156857 chrony_1.23-4.diff.gz
 9074028d3c473568a363c2f09de0126133934682 337216 chrony_1.23-4_amd64.deb
Checksums-Sha256: 
 9e3539d86be9233f5cc5d35370e5e17267e531fc0e238eeb34ab0582c104ee2b 1095 
chrony_1.23-4.dsc
 a17c1e4a04055911218d4d92d8a2de69e603fd91b8ec40d8cfd3c4617e7ce4a8 156857 
chrony_1.23-4.diff.gz
 49164568829ef24cb714746afddac63150800c9b35cd45d04d31b65c12b19d25 337216 
chrony_1.23-4_amd64.deb
Files: 
 02314a37a59d12e5989626340ea9faeb 1095 admin extra chrony_1.23-4.dsc
 b5b068fecd5f95cfd2a5d320aecf7f6a 156857 admin extra chrony_1.23-4.diff.gz
 b6575692af8da3d4d11e25538894b31f 337216 admin extra chrony_1.23-4_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQCVAwUBSRTdNfc1CeQKxb5hAQIsSgP/cC29MKlFrq//Exb/h/HQl/yqCh96wr9E
u7/PqGGxxc1lvVjcYzHEKQvPgyHVdWTArYChGAnGUu3y8bi6MvfpO2WeowpOOEBC
CkKQwua4icNd008deCoo2lzWjUK7oE2pquo6jOomZrSWwS0mpe1F7+OISe/YXrXa
kbCaNZLlaRY=
=W/0T
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to