Package: adjtimex
Version: 1.22-1
Severity: normal
During an upgrade while running CPU hog 'qemu' in
the background:
Setting up adjtimex (1.22-1) ...
Regulating system clock...done.
Comparing clocks (this will take 70 sec)...adjtimex: Invalid argument
done.
Adjusting system time by -380133 sec/day to agree with CMOS clock...done.
A four day adjustment.
It seems 'adjtimex' is quite clock & CPU dependent; if so, it could
check if the CPU was busy before making tests; or a maximum adjustment,
if exceeded, generates an error or else triggers some appropriate
response.
Hope this helps...
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages adjtimex depends on:
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
ii libc6 2.6.1-5 GNU C Library: Shared libraries
adjtimex recommends no packages.
-- debconf information:
* adjtimex/run_daemon: true
* adjtimex/compare_rtc: true
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
