Your message dated Sat, 29 Oct 2016 14:50:31 +0000
with message-id <[email protected]>
and subject line Bug#743444: fixed in adjtimex 1.29-9
has caused the Debian Bug report #743444,
regarding errors in the man page of adjtimex
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.)
--
743444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: adjtimex
Version: 1.29-2.2
Severity: minor
There are errors in the man page of adjtimex. A research on
manpages.debian.org shows they are there since ages. For this bug I am
referring to the version we have in Wheezy: http://tinyurl.com/koxklkj
The section about the option -t says that one tick is roughly equivalent
to 100ppm (in the case illustrated). A bit below, the section about the
option -f says:
> -f newfreq, --frequency newfreq
> Set the system clock frequency offset to newfreq. newfreq can
> be negative or positive, and gives a much finer adjustment than
> the --tick switch. When USER_HZ=100, the value is scaled such
> that newfreq = 65536 speeds up the system clock by about 1 ppm,
> or .0864 sec/day. Thus, all of these are about the same:
> --tick 9995 --frequency 32768000
> --tick 10000 --frequency 6553600
> --tick 10001 --frequency 0
> --tick 10002 --frequency -6553600
> --tick 10005 --frequency -32768000
> To see the acceptable range for newfreq, use --print and look at
> "tolerance", or try an illegal value (e.g. --tick 0).
Now, the five cases are not equivalent.
The first is subtracting 500ppm with -t (9995-10000)x100ppm, and adding
500ppm with the frequency (65535x5)x100ppm. It is equivalent and
symmetric with the fifth case, where 5 ticks are added (=500ppm) and
500ppm are reduced via the frequency. Both result in a no change to the
clock speed (0ppm added/subtracted)
The second, third and fourth case are all equivalent, but they add
100ppm to the clock speed instead:
- the second keeps the ticks at 10000, but adds 65535x100 to the
frequency, so 100ppm
- the second adds one tick (100ppm), but sets the frequency at 0, so 100ppm
- the third adds two ticks (200ppm) but subtracts 65535x100 to the
frequency, so 100ppm; the total is again 100ppm
There are many ways to make the five cases equivalent, e.g.: either
change 1, 5 to match 2, 3, 4, or vice versa. I'll leave it to the author
of the man page to decide which change fits best.
Kind Regards
-- Marco
--- End Message ---
--- Begin Message ---
Source: adjtimex
Source-Version: 1.29-9
We believe that the bug you reported is fixed in the latest version of
adjtimex, which is due to be installed in the Debian FTP archive.
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.
Roger Shimizu <[email protected]> (supplier of updated adjtimex 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: SHA512
Format: 1.8
Date: Sat, 29 Oct 2016 20:56:42 +0900
Source: adjtimex
Binary: adjtimex
Architecture: source
Version: 1.29-9
Distribution: unstable
Urgency: medium
Maintainer: Roger Shimizu <[email protected]>
Changed-By: Roger Shimizu <[email protected]>
Description:
adjtimex - kernel time variables configuration utility
Closes: 397182 743444 759399
Changes:
adjtimex (1.29-9) unstable; urgency=medium
.
* debian/patches:
- Add 07 patch to update manpage adjtimex.8:
. Add a few new timex status from kernel parameter.
Thanks to Chris Hiestand <[email protected]>. (Closes: #759399)
. Update the example to explain --frequency calculation.
Thanks to Marco Marongiu <[email protected]>.
(Closes: #743444)
* debian/contrib:
- Add a contrib script to calculate frequency from NTP drift file.
Thanks to <[email protected]>. (Closes: #397182)
Checksums-Sha1:
0e493125bda7a857c33c2814359ca00149d2f546 1844 adjtimex_1.29-9.dsc
32b08df54975c2769bb66ab76c5f95530dccdd74 29216 adjtimex_1.29-9.debian.tar.xz
Checksums-Sha256:
4cee86f2b0e49a6d38f09154968ad6730ebf03d964c29a17e20b457906568601 1844
adjtimex_1.29-9.dsc
3ffe1140a371b887eae1673ee6ce681caae254db3294d2ac84de073a532a271c 29216
adjtimex_1.29-9.debian.tar.xz
Files:
92298ae163738108dd322ba84254bcce 1844 admin optional adjtimex_1.29-9.dsc
a5a376abe876656dbb058e6c318e9695 29216 admin optional
adjtimex_1.29-9.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQI0BAEBCgAeBQJYFI9gFxxyb2dlcnNoaW1penVAZ21haWwuY29tAAoJEGxqzWQX
s6yx7dkP/3q1BS5YK/Njj0NumfC6zHUNYw+gj+Qtk6qP5qZfeoacgD8lrGZDuGe5
G6eLEZwv2BSHhJN8NtVBGbSECgNqoUeFP+tjgVMM+4DTxN/HjRTr/Yqvjw+wzpHH
1C2QllxzRiMFhfsajDNUjd6ge8th0cPtWILnrLe2wkixT2ARIK9VV9UgO+AwPPBk
1g8nkWiT/paVqg0uDXrpAxQZieZ44WGd3Ck8nI0gJXZ4jVrIPf9CpN360bT8v7MR
P9cFubqTEirE/LVQng8kv+FoNydl/Vq8vms64vf40rgEtsX869hgBpyxPYukBODg
HwvQp1Txttd6fnJbh8hbWa0aD2Mz2T5kpeSfC2dwC6V3j22YmRIumYLO2BcKN1oj
uNIBMZMhDZjkneG7KRmW1JMqbUPI/QzzWPuU/y4OkZzCiyamNAk1oa9nJpIb+3Jj
Ebi3BudE5KF+V56mE/jhlcU2z18e7yd57Bh87C7Npo5LGh2Cz3P+t1URoxP8nkv0
HOBieEMXwrXKU/BwkXS5OS3ogID+PIXAjl9ch2isHkBaAoPLIUUIJCqTy4Ex4inE
8gEu7CpnbHdol4FEnoGe+MCQcwWF8xSnFaeH13mWbJmvBR9sxtnfVVCqWhdz+ml7
81r+UCBTEb7n3pegJAPYyZxW75M2WY6gYzGH4MhmEXBWShK/KN5N
=CTP0
-----END PGP SIGNATURE-----
--- End Message ---
