Christian Perrier wrote: > Quoting James R. Van Zandt (jrvz@comcast.net): >> Yes, it always takes exactly 70 seconds. I see no benefit in being vague. A few "sudo time adjtimexconfig" runs confirm that it's seventy point something seconds, or very rarely seventy-one point something. > Will it always take 70 seconds in the future? > > If that is likely to change over time (maybe because the software does > additionnal checks or for whichever reason....), then either: > - one will forget to change the templates text accordingly > - the text willl be changed and a bunch of translations will need to > be adapted. The same figure is already mentioned in other places, including a commandline warning message, so it seems to me that the debconf template might as well be equally specific. Mind you, I'd still change the "70 sec" in the template; sec is dry wine! The abbreviation for "seconds" is either (informally) "sec." or (officially) "s"; but I'd write it in full as "70 seconds". -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Template: adjtimex/run_daemon Type: boolean Default: true _Description: Should adjtimex be run at installation and at every startup? Running adjtimex at system startup will set the kernel time parameters to the values in /etc/default/adjtimex. . You should not choose this option if you just want to use adjtimex to inspect the current parameters. Template: adjtimex/compare_rtc Type: boolean Default: true _Description: Run adjtimexconfig when adjtimex is installed or upgraded? The adjtimexconfig script will use adjtimex to find values for the kernel variables "tick" and "frequency" that will make the system clock approximately agree with the hardware clock (also known as the CMOS clock). It then saves these values in the configuration file /etc/default/adjtimex so the settings will be restored on every boot, when /etc/init.d/adjtimex runs. . The script takes 70 seconds to run, so running it for every upgrade may be a waste of time. Alternatively, you can run adjtimexconfig manually when needed, or determine the kernel variables by using other methods and set them manually in /etc/default/adjtimex.
Source: adjtimex
Section: admin
Priority: optional
Maintainer: James R. Van Zandt <jrv@debian.org>
Build-Depends: debhelper (>= 5), po-debconf
Standards-Version: 3.8.0
Package: adjtimex
Architecture: any
Depends: ${shlibs:Depends}, debconf | debconf-2.0
Suggests: ntpdate
Description: kernel time variables configuration utility
This package provides a utility to manipulate the kernel time variables. For
a machine connected to the Internet, or equipped with a precision
oscillator or radio clock, the best way to keep the system clock
accurate is using NTP (Network Time Protocol). However, for a standalone or intermittently
connected machine, you may use adjtimex instead to at least correct
for systematic drift. It can optionally adjust the system
clock using the CMOS clock as a reference, and can log times for
long-term estimation of drift rates.
--- ../adjtimex-1.26.pristine/debian/templates 2009-02-26 14:37:06.000000000 +0000
+++ debian/templates 2009-03-02 11:31:28.000000000 +0000
@@ -2,21 +2,23 @@
Type: boolean
Default: true
_Description: Should adjtimex be run at installation and at every startup?
- adjtimex can run at system startup to set the kernel time parameters to
- the values in /etc/default/adjtimex. Don't accept if you just want to
+ Running adjtimex at system startup will set the kernel time parameters to
+ the values in /etc/default/adjtimex.
+ .
+ You should not choose this option if you just want to
use adjtimex to inspect the current parameters.
Template: adjtimex/compare_rtc
Type: boolean
Default: true
-_Description: Should adjtimexconfig be run when adjtimex is installed or upgraded?
+_Description: Run adjtimexconfig when adjtimex is installed or upgraded?
The adjtimexconfig script will use adjtimex to find values for the kernel
- variables tick and frequency that will make the system clock approximately
+ variables "tick" and "frequency" that will make the system clock approximately
agree with the hardware clock (also known as the CMOS clock). It then
saves these values in the configuration file /etc/default/adjtimex so the
settings will be restored on every boot, when /etc/init.d/adjtimex runs.
.
- The script takes 70 sec to run. Alternatively, you can run adjtimexconfig
- yourself at a later time, or determine the kernel variables one of several
- other ways (see the adjtimex man page) and install them in
- /etc/default/adjtimex.
+ The script takes 70 seconds to run, so running it for every upgrade
+ may be a waste of time. Alternatively, you can run adjtimexconfig
+ manually when needed, or determine the kernel variables by using other
+ methods and set them manually in /etc/default/adjtimex.
--- ../adjtimex-1.26.pristine/debian/control 2009-02-26 14:37:06.000000000 +0000
+++ debian/control 2009-03-02 11:31:47.000000000 +0000
@@ -9,12 +9,12 @@
Architecture: any
Depends: ${shlibs:Depends}, debconf | debconf-2.0
Suggests: ntpdate
-Description: Utility to display or set the kernel time variables
- This program gives you raw access to the kernel time variables. For
+Description: kernel time variables configuration utility
+ This package provides a utility to manipulate the kernel time variables. For
a machine connected to the Internet, or equipped with a precision
oscillator or radio clock, the best way to keep the system clock
- correct is with ntpd. However, for a standalone or intermittently
+ accurate is using NTP (Network Time Protocol). However, for a standalone or intermittently
connected machine, you may use adjtimex instead to at least correct
- for systematic drift. adjtimex can optionally adjust the system
+ for systematic drift. It can optionally adjust the system
clock using the CMOS clock as a reference, and can log times for
long-term estimation of drift rates.